From 2f0e3e6733ba1d5640b747c1c9e1228202fad91b Mon Sep 17 00:00:00 2001 From: Matt Dorn Date: Thu, 11 Jul 2019 13:44:28 -0500 Subject: [PATCH] remove apply of RBAC definitions remove apply of RBAC definitions for up local example --- doc/helm/dev/developer_guide.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/doc/helm/dev/developer_guide.md b/doc/helm/dev/developer_guide.md index 31a3455f5de..4a9d6c45879 100644 --- a/doc/helm/dev/developer_guide.md +++ b/doc/helm/dev/developer_guide.md @@ -279,17 +279,15 @@ sudo mkdir -p /opt/helm/helm-charts sudo ln -s $PWD/helm-charts/ /opt/helm/helm-charts/ ``` -Create a Custom Resource Definition (CRD) and proper Role-Based Access Control -(RBAC) definitions for resource Foo. `operator-sdk` autogenerates these files +Create a Custom Resource Definition (CRD) for resource Foo. `operator-sdk` autogenerates this file inside of the `deploy` folder: ```sh kubectl create -f deploy/crds/foo_v1alpha1_foo_crd.yaml -kubectl create -f deploy/service_account.yaml -kubectl create -f deploy/role.yaml -kubectl create -f deploy/role_binding.yaml ``` +**NOTE:** When running the Helm operator locally, the `up local` command will default to using the kubeconfig file specified by `$KUBECONFIG` with a fallback to `$HOME/.kube/config` if not set. In this case, the autogenerated RBAC definitions do not need to be applied to the cluster. + Run the `up local` command: ```sh