From b284cb9910ea26775c4a0a31be8c4c3d2483dd63 Mon Sep 17 00:00:00 2001 From: ashish-billore Date: Tue, 17 Sep 2019 19:58:02 +0900 Subject: [PATCH] Updated command to start in-cluster deployment Updated the --image-pull-policy=Never option with default 'IfNotPresent'. 'Never' causes the pod to be in state: ErrImageNeverPull Kubernetes-commit: 7400cf937b9fcc31dc29caa8d90800940602b934 --- examples/in-cluster-client-configuration/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/in-cluster-client-configuration/README.md b/examples/in-cluster-client-configuration/README.md index 5aaf4956..83ad1a6b 100644 --- a/examples/in-cluster-client-configuration/README.md +++ b/examples/in-cluster-client-configuration/README.md @@ -37,7 +37,7 @@ kubectl create clusterrolebinding default-view --clusterrole=view --serviceaccou Then, run the image in a Pod with a single instance Deployment: - kubectl run --rm -i demo --image=in-cluster --image-pull-policy=Never + kubectl run --rm -i demo --image=in-cluster There are 4 pods in the cluster There are 4 pods in the cluster