K9s: Secret decoded content is not shown

Created on 21 Oct 2019  路  7Comments  路  Source: derailed/k9s






Describe the bug
this issue states that the describe of a secret should show it's content with Base 64 decoded values. But it does not work on version 0.9.2
https://github.com/derailed/k9s/issues/123

To Reproduce
create a secret and try to describe it
Expected behavior
data content in clear

Screenshots
If applicable, add screenshots to help explain your problem.

Versions (please complete the following information):

  • OS: OSX Mojave 10.14.6
  • K9s : 0.9.2
  • K8s v1.13.10-eks-5ac0f1

Additional context
Add any other context about the problem here.

question

Most helpful comment

Ah my mistake, I thought they meant they wanted describe to decode. Being able to press ctrl-x from the describe page would be nice.

All 7 comments

@sgandon Thank you for this report! In parity with kubectl, describe does not automatically decode the secret data. To see the base64 decoded secret playload you can use Ctrl-x

Thank a lot for this quick answer.
I did try Ctrl-x when the describe was shown and it did not work, I finally found that this is a command to be used on the secret selection.
I would be nice to have it implemented in the describe view as well.
What do you think ?

That would be handy...

Alternatively, if it''s not going to work on the describe screen, it'd be nice to take it off of the suggested shortcuts up top while in a description. I often see it up there and forget it won't work on that screen until I try it.

I would be nice to have it implemented in the describe view as well.

馃憥

Keep the parity. Use ctrl-x when you need to decode.

@RothAndrew ... so using ctrl-x to decode from the secrets list is ok, but also being able to hit ctrl-x while in a secret describe is a bad thing? Why?

Ah my mistake, I thought they meant they wanted describe to decode. Being able to press ctrl-x from the describe page would be nice.

Was this page helpful?
0 / 5 - 0 ratings