-
Notifications
You must be signed in to change notification settings - Fork 59
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
Operator no longer includes annotations within the created secret #144
Comments
I see the commit where it was changed IMO, we should allow users to add extra annotations. One option could be to add a
|
Thank you for raising this with us. |
Hi, any progress on this, or a workaround perhaps using kustomize? |
I forked it and added the functionality back |
Any updates on this @edif2008 ? |
Still not fixed? Come on.... |
Hi folks, is there a plan to implement this in the near future? As said by OP it used to work but was reverted on afa076d. Our use case is for argocd secrets, it uses labels to pick up the different types of secrets. thanks |
Your environment
Operator Version: v1.6.0
Connect Server Version: 1.5.7
Kubernetes Version: 1.23.9
What happened?
In version 1.3.0 of the operator, any annotation I added to the operator would be propagated to the resulting secret. Now, none of my annotations are added.
What did you expect to happen?
I expected the resulting secret to have the annotations I set
Steps to reproduce
Notes & Logs
The text was updated successfully, but these errors were encountered: