-
Notifications
You must be signed in to change notification settings - Fork 345
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
failed to create or get service for metrics #461
Comments
@jpkrohling Hello, you need to add the following to your role.yaml file, and it should fix this problem, as we are putting the Deployment of the operator as the owner to the OwnerRef of the Service object on creation:
Docs on this in operator-sdk. See full role.yaml file here -> https://github.com/operator-framework/operator-sdk-samples/blob/bd30254f3a7e3943fdbae33e9b6992bce1e07755/memcached-operator/deploy/role.yaml Let me know if this doesn't work for you! |
Spot on, @lilic! Would you be open to review the PR that reinstates the metrics service? |
Currently, the Jaeger Operator fails to start in OpenShift due to the following message:
This log message is recorded with
fatal
level, making the operator to simply exit upon this failure. Operators created with newer versions of the SDK have this set toinfo
instead. This of course doesn't fix the underlying problem, but I think we should not crash the operator because of this failure.The text was updated successfully, but these errors were encountered: