-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Kubeseal example not working #288
Comments
Hey thanks for reporting the bug. For your specific error: make sure you're using an appropiate kubeseal binary for the sealed secrets controller that you installed. On the other hand, try to get a list of the services in the Sealed Secrets namespace. Apparently there's one missing, but it could be due to a mismatch in the binary client. Finally, I'm not sure if my civo account is still active but if it is I will try to reproduce it and upgrade the manifest to a newer version of Sealed Secrets. |
I've contacted Civo support team to see if they can help me by providing a small cluster for a week so I can upgrade the manifest in the marketplace and help you. |
Thank you |
@exocode in the meantime, please download the kubeseal binary corresponding to the controller version in marketplace (0.12.4) and see if the issue persists. |
Quay is on again... I followed the instructions: of v0.12.4 here: https://github.com/bitnami-labs/sealed-secrets/releases/tag/v0.12.4 (using Mac)
|
(tried everything on a 1 node cluster small with no "Marketplace" apps installed. Only applied your manifest: |
Hi @exocode can you raise a PR to fix it on the marketplace app side ? |
Hi @soukron I tried your sealsecret installation manifest
This issue is a:
Install Kubeseal via Marketplace
Run the post install example
❯ echo -n bar | kubectl create secret generic mysecret --dry-run --from-file=foo=/dev/stdin -o json >mysecret.json
result
W1222 13:21:46.889535 17129 helpers.go:555] --dry-run is deprecated and can be replaced with --dry-run=client.
ok, so far so good change the --dry-run part:
❯ echo -n bar | kubectl create secret generic mysecret --dry-run=client --from-file=foo=/dev/stdin -o json >mysecret.json
But step 3 fails definitely:
Could it be that ArgoCD is somehow interferencing?
These are all my installed apps:
The text was updated successfully, but these errors were encountered: