From eaf8b43d6cbd23464bb25c1e47605ca0135530e7 Mon Sep 17 00:00:00 2001 From: mohamed chiheb ben jemaa Date: Tue, 9 Jul 2019 12:10:02 +0100 Subject: [PATCH] change image registry (#15326) --- .../docs/tasks/administer-cluster/namespaces-walkthrough.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/namespaces-walkthrough.md b/content/en/docs/tasks/administer-cluster/namespaces-walkthrough.md index 9eb8692a8f..e92e8ca476 100644 --- a/content/en/docs/tasks/administer-cluster/namespaces-walkthrough.md +++ b/content/en/docs/tasks/administer-cluster/namespaces-walkthrough.md @@ -225,7 +225,7 @@ At this point, all requests we make to the Kubernetes cluster from the command l Let's create some contents. ```shell -kubectl run snowflake --image=kubernetes/serve_hostname --replicas=2 +kubectl run snowflake --image=k8s.gcr.io/serve_hostname --replicas=2 ``` We have just created a deployment whose replica size is 2 that is running the pod called `snowflake` with a basic container that just serves the hostname. Note that `kubectl run` creates deployments only on Kubernetes cluster >= v1.2. If you are running older versions, it creates replication controllers instead. @@ -266,7 +266,7 @@ kubectl get pods Production likes to run cattle, so let's create some cattle pods. ```shell -kubectl run cattle --image=kubernetes/serve_hostname --replicas=5 +kubectl run cattle --image=k8s.gcr.io/serve_hostname --replicas=5 kubectl get deployment ```