-
Notifications
You must be signed in to change notification settings - Fork 9
serviceAccountName listed when rbacEnabled=false #255
Description
Is this a BUG or FEATURE REQUEST?:
BUG
Did you review https://istio.io/help/ and existing issues to identify if this is already solved or being worked on?: Y
Bug:
Y/N
What Version of Istio and Kubernetes are you using, where did you get Istio from, Installation details
istioctl version
Version: 0.6.0
GitRevision: 2cb09cdf040a8573330a127947b11e5082619895
User: root@a28f609ab931
Hub: docker.io/istio
GolangVersion: go1.9
BuildStatus: Clean
kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.1", GitCommit:"3a1c9449a956b6026f075fa3134ff92f7d55f812", GitTreeState:"clean", BuildDate:"2018-01-04T11:52:23Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"", Minor:"", GitVersion:"v1.9.4", GitCommit:"bee2d1505c4fe820744d26d41ecd3fdd4a3d6546", GitTreeState:"clean", BuildDate:"2018-03-21T21:48:36Z", GoVersion:"go1.9.1", Compiler:"gc", Platform:"linux/amd64"}
Also, running on Minikube:
minikube version: v0.25.2
I cloned Istio's source code to get Istio (due to a bug in the Helm charts and me needing to manually package the helm chart from source).
Is Istio Auth enabled or not ?
Did you install istio.yaml, istio-auth.yaml....
No
What happened:
Deploying with rbacEnabled=false
fails with a timeout. This seems to me to be related to RBAC. I made some changes (I attached a diff of the changes I made), and after that, the helm install succeeded.
I figured this might work after noticing the prometheus Deployment object wrapping the serviceAccountName in the conditional for .Values.global.rbacEnabled
, but that was missing in various other places.
What you expected to happen:
I expect the helm install to succeed.
How to reproduce it:
- Clone the Istio source
- Run
helm install istio/install/kubernetes/helm/istio --name istio --namespace=istio-system --set global.rbacEnabled=false