From 4f0d3d501ea53ae89ad4a63139d3cd568279240e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Manuel=20R=C3=BCger?= Date: Fri, 6 Apr 2018 21:16:09 +0200 Subject: [PATCH] Explain what the auth field in the secret encodes (#7996) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Manuel Rüger --- .../pull-image-private-registry.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/tasks/configure-pod-container/pull-image-private-registry.md b/docs/tasks/configure-pod-container/pull-image-private-registry.md index 6991e86455..cfaa8f107b 100644 --- a/docs/tasks/configure-pod-container/pull-image-private-registry.md +++ b/docs/tasks/configure-pod-container/pull-image-private-registry.md @@ -93,6 +93,14 @@ The output is similar to this: {"auths":{"yourprivateregistry.com":{"username":"janedoe","password":"xxxxxxxxxxx","email":"jdoe@example.com","auth":"c3R...zE2"}}} +To understand what is in the `auth` field, convert the base64-encoded data to a readable format: + + echo "c3R...zE2" | base64 -d + +The output, username and password concatenated with a `:`, is similar to this: + + janedoe:xxxxxxxxxxx + Notice that the Secret data contains the authorization token similar to your local `~/.docker/config.json` file. You have successfully set your Docker credentials as a Secret called `regcred` in the cluster.