Skip to content
Permalink
Browse files

changed example domain to be **example.com** (#14740)

**your.private.registry.example.com** is a better choice of domain name for a non-existing sample domain name than calling it **yourprivateregistry.com**

refer #14283
  • Loading branch information...
raja-anbazhagan authored and k8s-ci-robot committed Jun 6, 2019
1 parent 07812a5 commit 1fbcb30b4f74668fb1888c5b40c5aa47d4aa8319
Showing with 2 additions and 2 deletions.
  1. +2 −2 content/en/docs/tasks/configure-pod-container/pull-image-private-registry.md
@@ -153,7 +153,7 @@ kubectl get secret regcred --output="jsonpath={.data.\.dockerconfigjson}" | base
The output is similar to this:

```json
{"auths":{"yourprivateregistry.com":{"username":"janedoe","password":"xxxxxxxxxxx","email":"jdoe@example.com","auth":"c3R...zE2"}}}
{"auths":{"your.private.registry.example.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:
@@ -187,7 +187,7 @@ wget -O my-private-reg-pod.yaml https://k8s.io/examples/pods/private-reg-pod.yam
In file `my-private-reg-pod.yaml`, replace `<your-private-image>` with the path to an image in a private registry such as:

```none
yourprivateregistry.com/janedoe/jdoe-private:v1
your.private.registry.example.com/janedoe/jdoe-private:v1
```

To pull the image from the private registry, Kubernetes needs credentials.

0 comments on commit 1fbcb30

Please sign in to comment.
You can’t perform that action at this time.