kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Correct secret creation command 

Private Registry FQDN also needs to be included in secret creation, otherwise Kubernetes will not be able to pull images.
This commit is contained in:
Harsh Choudhary 2017-04-18 14:42:26 +05:30 committed by Andrew Chen
parent b17c1e6b82
commit 800f1b588d
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/tasks/configure-pod-container/pull-image-private-registry.md
View File

@ -47,10 +47,11 @@ The output contains a section similar to this:
Create a Secret named `regsecret`:
kubectl create secret docker-registry regsecret --docker-username=<your-name> --docker-password=<your-pword> --docker-email=<your-email>
kubectl create secret docker-registry regsecret --docker-server=<your-registry-server> --docker-username=<your-name> --docker-password=<your-pword> --docker-email=<your-email>
where:
* `<your-registry-server>` is your Private Docker Registry FQDN.
* `<your-name>` is your Docker username.
* `<your-pword>` is your Docker password.
* `<your-email>` is your Docker email.
@ -87,7 +88,7 @@ readable format:
The output is similar to this:
{"https://index.docker.io/v1/":{"username":"janedoe","password":"xxxxxxxxxxx","email":"jdoe@example.com","auth":"c3RldmU1MzpTdGV2ZURvY2tAIzE2"}}
{"yourprivateregistry.com":{"username":"janedoe","password":"xxxxxxxxxxx","email":"jdoe@example.com","auth":"c3RldmU1MzpTdGV2ZURvY2tAIzE2"}}
Notice that the secret data contains the authorization token from your
`config.json` file.