Closed Barsonax closed 2 months ago
@Barsonax I encountered the same issue and resolved it by changing the encoding of the created secret to UTF-8. I also had a similar problem with the fetched certificate, which wasn't encoded in UTF-8 either.
Yeah that seems to fix the problem. So changing step 1 to this will make it work (using powershell):
kubectl create secret generic mysecret --dry-run=client --from-literal=username=admin -o json | Out-File -Encoding "UTF8" "mysecret.json"
If its not easy to fix this in kubeseal I think it would be fine if kubeseal just gave a descriptive error telling you the encoding needs to be UTF8.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Bump
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 7 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
This shouldn't be closed as it's a real issue that has not been fixed yet
This is nor resolved. At least some error message would be helpful
@Barsonax @tadeasbronis I created a PR #1580, but it needs to be merged.
Which component: kubeseal 0.27.0
Describe the bug kubeseal is creating an empty file with no contents
To Reproduce
kubectl create secret generic mysecret --dry-run=client --from-literal=username=admin -o json > mysecret.json
kubeseal -f mysecret.json -w mysealedsecret.json
mysealedsecret.json
will be emptyExpected behavior Content in the file
Version of Kubernetes:
Additional context This is on windows 11 (Version 10.0.22631 Build 22631)
kubeseal with --raw does produce output