-
Notifications
You must be signed in to change notification settings - Fork 344
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
Fixed permissions for ServiceMonitor objects #831
Fixed permissions for ServiceMonitor objects #831
Conversation
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
@jkandasa I tested this on a real OpenShift 4.2.2 cluster, but would you please also give this one a test? |
@jpkrohling sure, can you please share the image details? |
Yes, sorry. Here it is: |
@pavolloffay, @objectiser I think this one should be included for 1.16.0. Given that it only adds permissions, I'd say that the risk of breaking things is low. |
I'm merging, but I'm ready to go back to this in case @jkandasa finds any problems. |
@jpkrohling I installed this operator, Initial log:
I killed the pod and the log from recreated pod:
I deployed all-in-one jaeger service and see the following error message. I do not see any impact on jaeger service deployment. Keep on reporting this error
|
This PR fixes the permissions problems related to the creation of
ServiceMonitor
objects. After this PR, this is how a Jaeger Operator bootstrap looks like:If the pod is killed and a new operator is started in the same namespace, the following is seen:
Fixes #804.
Signed-off-by: Juraci Paixão Kröhling [email protected]