Skip to content
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

Unable to re-encrypt secrets with error: 'cannot re-encrypt secret: no endpoints available for service "http:sealed-secrets:"' #722

Closed
k8soneill opened this issue Jan 21, 2022 · 1 comment · Fixed by #726
Assignees
Labels

Comments

@k8soneill
Copy link

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

  1. Deploy sealed-secrets app to sealed secrets namespace using helm chart version 2.1.0
  2. Create a test sealed secret with original key
  3. Force the controller to generate a new key
  4. Disable original key
  5. 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
@juan131
Copy link
Collaborator

juan131 commented Jan 27, 2022

Thanks so much for reporting this @koneill94 !! I just send a PR to address it

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants