-
Notifications
You must be signed in to change notification settings - Fork 661
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
Unseal updated secret: Precondition failed #898
Labels
backlog
Issues/PRs that will be included in the project roadmap
Comments
alemorcuq
added
backlog
Issues/PRs that will be included in the project roadmap
and removed
triage
Issues/PRs that need to be reviewed
labels
Aug 25, 2022
Same here :) it seems to be related to the replace object : |
Any news ? because theSealedSecretsUnsealErrorHigh alert (mixin) generate lot of false positive. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which component:
Controller
Describe the bug
I have a sealed secret successfully injected into the cluster, which was encrypted. I wanted to add another key to it, so i edited the cleartext YAML, generated another sealed secret from it, and injected it into the cluster. The controller was unable to decrypt it:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The newly injected sealed secret gets decrypted
Version of Kubernetes:
kubectl version
:I know that the kubernetes is a bit outdated. It is a managed k8s by an inhouse openstack provider, and they do not offer a newer version yet.
The text was updated successfully, but these errors were encountered: