From b82bf962039d98889f9e5806bafaaae57255ac70 Mon Sep 17 00:00:00 2001 From: adisky Date: Mon, 19 Nov 2018 08:10:10 +0530 Subject: [PATCH] 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 secret --- content/en/docs/tasks/administer-cluster/encrypt-data.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/tasks/administer-cluster/encrypt-data.md b/content/en/docs/tasks/administer-cluster/encrypt-data.md index e06ceda9f8..405b1aa96f 100644 --- a/content/en/docs/tasks/administer-cluster/encrypt-data.md +++ b/content/en/docs/tasks/administer-cluster/encrypt-data.md @@ -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