From 164fe70df7722ed8fa4788459f39113e89b8e7a6 Mon Sep 17 00:00:00 2001 From: Donovan Muller Date: Wed, 14 Dec 2016 00:51:23 +0200 Subject: [PATCH] Replace cluster-view with cluster-reader Fixes #72 --- readme.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/readme.md b/readme.md index 88d340fb..0c090797 100644 --- a/readme.md +++ b/readme.md @@ -390,10 +390,10 @@ For earlier version it needs to be specified as an env var to the pod. A quick w #### Service Account -For distros of Kubernetes that support more fine-grained role-based access within the cluster, you need to make sure a pod that runs with spring-cloud-kubernetes has access to the Kubernetes API. For example, OpenShift has very comprehensive security measures that are on by default (typically) in a shared cluster. For any service accounts you assign to a deployment/pod, you need to make sure it has the correct roles. For example, you can add `cluster-view` permissions to your `default` service account depending on the project you're in: +For distros of Kubernetes that support more fine-grained role-based access within the cluster, you need to make sure a pod that runs with spring-cloud-kubernetes has access to the Kubernetes API. For example, OpenShift has very comprehensive security measures that are on by default (typically) in a shared cluster. For any service accounts you assign to a deployment/pod, you need to make sure it has the correct roles. For example, you can add `cluster-reader` permissions to your `default` service account depending on the project you're in: ``` -oc policy add-role-to-user cluster-view system:serviceaccount::default +oc policy add-role-to-user cluster-reader system:serviceaccount::default ``` ### Building