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
Which component:
Sealed secrets controller v0.17.2 and kubeseal version 0.17.2
Describe the bug
I'm attempting some DR testing and when I run the following command: kubeseal --controller-namespace sealed-secrets --controller-name sealed-secrets --re-encrypt < sealed-secret2.yaml > tmp.yaml
It returns error: cannot re-encrypt secret: no endpoints available for service "http:sealed-secrets:"
I had originally had the problem described here: #694 but upgrading kubeseal to 0.17.2 fixed this however when I attempt re-encryption of a sealed secret it occurrs.
To Reproduce
Deploy sealed-secrets app to sealed secrets namespace using helm chart version 2.1.0
Create a test sealed secret with original key
Force the controller to generate a new key
Disable original key
Attempt to re-encrypt secret using kubeseal --controller-namespace sealed-secrets --controller-name sealed-secrets --re-encrypt < sealed-secret2.yaml > tmp.yaml
Expected behavior
I expect the tmp.yaml to include a re-encrypted secret.
Version of Kubernetes:
Client Version: 4.8.18
Server Version: 4.8.24
Kubernetes Version: v1.21.6+c180a7c
The text was updated successfully, but these errors were encountered:
Which component:
Sealed secrets controller v0.17.2 and kubeseal version 0.17.2
Describe the bug
I'm attempting some DR testing and when I run the following command:
kubeseal --controller-namespace sealed-secrets --controller-name sealed-secrets --re-encrypt < sealed-secret2.yaml > tmp.yaml
It returns error: cannot re-encrypt secret: no endpoints available for service "http:sealed-secrets:"
I had originally had the problem described here: #694 but upgrading kubeseal to 0.17.2 fixed this however when I attempt re-encryption of a sealed secret it occurrs.
To Reproduce
kubeseal --controller-namespace sealed-secrets --controller-name sealed-secrets --re-encrypt < sealed-secret2.yaml > tmp.yaml
Expected behavior
I expect the tmp.yaml to include a re-encrypted secret.
Version of Kubernetes:
The text was updated successfully, but these errors were encountered: