-
Notifications
You must be signed in to change notification settings - Fork 72
RMQ operator can't import secrest created by External-secrets operator #929
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
Comments
This issue has been marked as stale due to 60 days of inactivity. Stale issues will be closed after a further 30 days of inactivity; please remove the stale label in order to prevent this occurring. |
Not stale |
I don't see how the user controller could be setting an owner reference on an external secret, given that it doesn't even watch them, see: messaging-topology-operator/main.go Lines 234 to 246 in 870860b
messaging-topology-operator/controllers/topology_controller.go Lines 224 to 229 in 870860b
Some YAML to reproduce the problem would be most welcome. |
Describe the bug
RMQ operator wants to set ownerRef on imported secrets to user
To Reproduce
Steps to reproduce the behavior:
create a secret with ownerRef (like with external-secrets and setting the creationPolicy to Owner)
create rmq user with imported secret
the user will throw an error in its status, claming it can't take ownership of the secret
Expected behavior
the operator should not take control of imported secrets
Screenshots
If applicable, add screenshots to help explain your problem.
Version and environment information
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: