Redirect to decoding a secret (#10594)
In this Document Encrypting Secret data at REST, the example to verify decrypt secret is bit confusing, on running $ kubectl describe secret secret1 -n default "should match mykey: mydata" never match because data is enoded, This commit redirects it to decoding the secretpull/11105/head
parent
b5a09f68de
commit
b82bf96203
|
@ -146,7 +146,8 @@ program to retrieve the contents of your secret.
|
|||
kubectl describe secret secret1 -n default
|
||||
```
|
||||
|
||||
should match `mykey: mydata`
|
||||
should match `mykey: bXlkYXRh`, mydata is encoded, check [decoding a secret](/docs/concepts/configuration/secret#decoding-a-secret) to
|
||||
completely decode the secret.
|
||||
|
||||
|
||||
## Ensure all secrets are encrypted
|
||||
|
|
Loading…
Reference in New Issue