From 61a24777f8d987eeddd6b4a294ffb497efd5e217 Mon Sep 17 00:00:00 2001 From: Davanum Srinivas Date: Fri, 28 Sep 2018 14:46:01 -0400 Subject: [PATCH] Add missing step to in-cluster-client-configuration example If the permissions are not setup correctly the example fails. Change-Id: I167ef68be66f8b56740236ae475c3b7fdcc0dfb5 Kubernetes-commit: d222c310aaa4ce8777094f4a37a920982aff794d --- examples/in-cluster-client-configuration/README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/examples/in-cluster-client-configuration/README.md b/examples/in-cluster-client-configuration/README.md index 811b750c..eaa10e0f 100644 --- a/examples/in-cluster-client-configuration/README.md +++ b/examples/in-cluster-client-configuration/README.md @@ -25,7 +25,13 @@ build the image on Minikube: docker build -t in-cluster . If you are not using Minikube, you should build this image and push it to a registry -that your Kubernetes cluster can pull from. +that your Kubernetes cluster can pull from. If you have RBAC enabled, use the following +snippet to create role binding which will grant the default service account view +permissions. + +``` +kubectl create clusterrolebinding default-view --clusterrole=view --serviceaccount=default:default +``` Then, run the image in a Pod with a single instance Deployment: