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

Incomplete decoded secrets #2693

Open
marcofranssen opened this issue May 7, 2024 · 0 comments
Open

Incomplete decoded secrets #2693

marcofranssen opened this issue May 7, 2024 · 0 comments

Comments

@marcofranssen
Copy link

marcofranssen commented May 7, 2024




Describe the bug

When decoding the following hypothetical secret {ofUfac]>t[898dfs it only shows the first part of the secret up till the [ character in the secret like this {ofUfac]>t.

So in essence as

- {ofUfac]>t[898dfs
+ {ofUfac]>t

To Reproduce
Steps to reproduce the behavior:

  1. Create a secret like this {ofUfac]>t[898dfs
  2. Navigate to the secret in k9s
  3. Press x to decode the secret
  4. The decoded secret shows as {ofUfac]>t
  5. Now decode the secret using kubectl (kubectl get secret my-secret -o jsonpath='{.data.password}' | base64 -d)
  6. The decoded secret shows correctly as {ofUfac]>t[898dfs

Historical Documents

Expected behavior

Secrets with special characters decode properly from k9s.

Screenshots

N.A.

Versions (please complete the following information):

  • OS: [e.g. OSX] MacOS Sonoma 14.4.1
  • K9s: [e.g. 0.1.0] 0.32.4
  • K8s: [e.g. 1.11.0] EKS 1.28

Additional context

So far only detected it for a secret containing [ at which it stops processing.

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

No branches or pull requests

1 participant