-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Ingress or Route for Jaeger UI #255
Create Ingress or Route for Jaeger UI #255
Conversation
ef41639
to
aa2f1c9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we add a test for OpenShift Routes and Ingresses?
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #255 +/- ##
==========================================
+ Coverage 60.69% 61.58% +0.89%
==========================================
Files 39 39
Lines 2984 3113 +129
==========================================
+ Hits 1811 1917 +106
- Misses 1076 1094 +18
- Partials 97 102 +5
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
* if jaegerQuery is enabled, create an Ingress or Route object by default, depending on the OpenShift.Route feature gate * show an error if Ingress or Route is enabled but jaegerQuery is disabled Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
…ftRoute Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
…me, check if route is enabled but feature gate is disabled
…S by default Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
ac57238
to
1263485
Compare
Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
1263485
to
851ec26
Compare
I added an assertion for the ingress in the smoketest-with-jaeger e2e. I'm currently thinking how to make one for Route - the problem is we need to enable the OpenShiftRoutes feature gate in the test. I'm unsure if I should really update the operator configmap and restart the operator inside a kuttl test? Parallel kuttl tests will then fail of course, and imho the tests should not restart or update the operator's configuration. Alternatively we could remove this feature gate and auto-detect the availability of openshift route. wdyt? |
That is one of the reasons why I don't like running the tests in parallel. I agree about the modification of the operator for the tests but... it is a common use case to test the different operator features. The last step of the test can be reverting back the changes done to the operator.
I don't have a strong opinion but, during some discussions, I understand the team prefers to use feature gates because it makes it easier to maintain the operators (because you enable or disable features instead of just detecting them). I don't have a strong opinion about this. @pavolloffay, @frzifus or @rubenvp8510 will provide a better answer than me about this topic. |
Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
I've now changed the webhook to not enable any type of ingress by default due to security reasons as @frzifus mentioned. I updated the Makefile to install the OpenShift router, and enable the feature gate (because now in e2e tests we always have the Not sure why the "upload coverage report" step fails, the unit tests pass though. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💪
utilruntime.Must(tempov1alpha1.AddToScheme(scheme)) | ||
utilruntime.Must(configtempov1alpha1.AddToScheme(scheme)) | ||
utilruntime.Must(configv1alpha1.AddToScheme(scheme)) | ||
utilruntime.Must(routev1.Install(scheme)) | ||
utilruntime.Must(openshiftoperatorv1.Install(scheme)) | ||
utilruntime.Must(configv1.Install(scheme)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to register routes here too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They're already registered: utilruntime.Must(routev1.Install(scheme))
(afaics it was part of some gateway PR).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ups :D
TODO: