Fix dockerhub URL
This commit is contained in:
parent
a4e48ec21a
commit
18c22d133e
|
|
@ -9,18 +9,13 @@ weight: 100
|
||||||
This page shows how to create a Pod that uses a Secret to pull an image from a
|
This page shows how to create a Pod that uses a Secret to pull an image from a
|
||||||
private Docker registry or repository.
|
private Docker registry or repository.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## {{% heading "prerequisites" %}}
|
## {{% heading "prerequisites" %}}
|
||||||
|
|
||||||
|
|
||||||
* {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
|
* {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
|
||||||
|
|
||||||
* To do this exercise, you need a
|
* To do this exercise, you need a
|
||||||
[Docker ID](https://docs.docker.com/docker-id/) and password.
|
[Docker ID](https://docs.docker.com/docker-id/) and password.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<!-- steps -->
|
<!-- steps -->
|
||||||
|
|
||||||
## Log in to Docker
|
## Log in to Docker
|
||||||
|
|
@ -106,7 +101,8 @@ kubectl create secret docker-registry regcred --docker-server=<your-registry-ser
|
||||||
|
|
||||||
where:
|
where:
|
||||||
|
|
||||||
* `<your-registry-server>` is your Private Docker Registry FQDN. (https://index.docker.io/v1/ for DockerHub)
|
* `<your-registry-server>` is your Private Docker Registry FQDN.
|
||||||
|
Use `https://index.docker.io/v2/` for DockerHub.
|
||||||
* `<your-name>` is your Docker username.
|
* `<your-name>` is your Docker username.
|
||||||
* `<your-pword>` is your Docker password.
|
* `<your-pword>` is your Docker password.
|
||||||
* `<your-email>` is your Docker email.
|
* `<your-email>` is your Docker email.
|
||||||
|
|
@ -192,7 +188,8 @@ your.private.registry.example.com/janedoe/jdoe-private:v1
|
||||||
```
|
```
|
||||||
|
|
||||||
To pull the image from the private registry, Kubernetes needs credentials.
|
To pull the image from the private registry, Kubernetes needs credentials.
|
||||||
The `imagePullSecrets` field in the configuration file specifies that Kubernetes should get the credentials from a Secret named `regcred`.
|
The `imagePullSecrets` field in the configuration file specifies that
|
||||||
|
Kubernetes should get the credentials from a Secret named `regcred`.
|
||||||
|
|
||||||
Create a Pod that uses your Secret, and verify that the Pod is running:
|
Create a Pod that uses your Secret, and verify that the Pod is running:
|
||||||
|
|
||||||
|
|
@ -201,11 +198,8 @@ kubectl apply -f my-private-reg-pod.yaml
|
||||||
kubectl get pod private-reg
|
kubectl get pod private-reg
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## {{% heading "whatsnext" %}}
|
## {{% heading "whatsnext" %}}
|
||||||
|
|
||||||
|
|
||||||
* Learn more about [Secrets](/docs/concepts/configuration/secret/).
|
* Learn more about [Secrets](/docs/concepts/configuration/secret/).
|
||||||
* Learn more about [using a private registry](/docs/concepts/containers/images/#using-a-private-registry).
|
* Learn more about [using a private registry](/docs/concepts/containers/images/#using-a-private-registry).
|
||||||
* Learn more about [adding image pull secrets to a service account](/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account).
|
* Learn more about [adding image pull secrets to a service account](/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account).
|
||||||
|
|
@ -213,5 +207,3 @@ kubectl get pod private-reg
|
||||||
* See [Secret](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#secret-v1-core).
|
* See [Secret](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#secret-v1-core).
|
||||||
* See the `imagePullSecrets` field of [PodSpec](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core).
|
* See the `imagePullSecrets` field of [PodSpec](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue