From 9c1fd9dcfe0b56ef727cae21c64afa99105d472e Mon Sep 17 00:00:00 2001 From: Ismail Alidzhikov Date: Tue, 16 Jul 2019 16:15:26 +0300 Subject: [PATCH] Fix serve_hostname image (#15416) Signed-off-by: ialidzhikov --- content/en/docs/tasks/administer-cluster/namespaces.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/namespaces.md b/content/en/docs/tasks/administer-cluster/namespaces.md index d8d7e9b827..3c2c974b8e 100644 --- a/content/en/docs/tasks/administer-cluster/namespaces.md +++ b/content/en/docs/tasks/administer-cluster/namespaces.md @@ -258,7 +258,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. @@ -298,7 +298,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 ```