You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
2022/08/01 11:27:52 Error updating SealedSecret dls-backend-test/arangodb status: Operation cannot be fulfilled on sealedsecrets.bitnami.com "arangodb": StorageError: invalid object, Code: 4, Key: /registry/bitnami.com/sealedse
crets/dls-backend-test/arangodb, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 5ae127fc-d895-4c93-82c6-979aae7d00a8, UID in object meta:
To Reproduce
Steps to reproduce the behavior:
Create a sealed secret
Inject it to the cluster, verify that it gets decrypted correctly
Edit the underlying cleartext yaml, add another key
Create a sealed secret from the modified YAML - same name, same namespace
Inject the new sealed secret to the cluster, effectively overwriting the old manifest
Expected behavior
The newly injected sealed secret gets decrypted
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
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: