interesting as I can run the chart manually with that flag a

Question

interesting as I can run the chart manually with that flag and have it go to `kube tools`

microscopic-florist-22719 · Answer

Hmmm interesting Let me take a look at the chart

fresh-umbrella-15520 · Answer

it s a copy of the stable datadog

microscopic-florist-22719 · Answer

Looking at the stable datadog template it doesn t seem to reference ` Release Namespace` anywhere What s the precise command you re using to install the chart

fresh-umbrella-15520 · Answer

helm install name datadog stable datadog tiller namespace=kube tools namespace=kube tools f override yaml

fresh-umbrella-15520 · Answer

I have used a datadog namespace too w o issue I can update the chart with that key

fresh-umbrella-15520 · Answer

Possible that we have super god tiller in that namespace and this is tillerless

fresh-umbrella-15520 · Answer

don t waste anymore time on it I will mess with the chart

microscopic-florist-22719 · Answer

Sounds good

fresh-umbrella-15520 · Answer

I ll let you know if I get it working

creamy-potato-29402 · Answer

< fresh umbrella 15520> I can take a look at this what is the helm chart version

fresh-umbrella-15520 · Answer

I think I got it just running into an RBAC perms deal i GKE

creamy-potato-29402 · Answer

< fresh umbrella 15520> Oh I think I know what s happening What we re doing is equivalent to `helm template` rather than `helm install` So if you re expecting Tiller to do something sparkles magic sparkles then it won t get done

fresh-umbrella-15520 · Answer

yeah working through it now

creamy-potato-29402 · Answer

I will be curious to see if you have feedback about how we should be presenting this to users

fresh-umbrella-15520 · Answer

will do I was using helm with a `god` tiller so it could create the roles and rolebindings that is the part I am working through now using tillerless

creamy-potato-29402 · Answer

You probably will have to do that work anyway because they re getting rid of Tiller slightly smiling face

fresh-umbrella-15520 · Answer

I got it to work

fresh-umbrella-15520 · Answer

Since I was using tiller that had a cluster admin role I had not granted those perms to my GKE user

fresh-umbrella-15520 · Answer

``` kubectl create clusterrolebinding cluster admin binding clusterrole cluster admin user USER ACCOUNT ```

fresh-umbrella-15520 · Answer

You must grant your user the ability to create roles in Kubernetes by running the following command USER ACCOUNT is the user s email address

creamy-potato-29402 · Answer

how did you figure this out < fresh umbrella 15520> Maybe we can bake it into the status messages slightly smiling face

fresh-umbrella-15520 · Answer

I was under the assumption it was running as my account since tiller was out of the picture Then < flaky receptionist 88878> mentioned about my email address for GKE and roles

creamy-potato-29402 · Answer

that whole stack GKE auth stack is super confusing and secretly my mission is to make all auth errors from it trivially debuggable

fresh-umbrella-15520 · Answer

I will try this out tomorrow on EKS as that we are using SAML and mapping to groups roles in k8s

creamy-potato-29402 · Answer

sick

fresh-umbrella-15520 · Answer

I am new to GKE so those small auth differences and I was testing on home lab stuff

creamy-potato-29402 · Answer

Yeah for our GKE library we have to generate a kubeconfig file that is compliant with their undocumented auth spec and it was a total nightmare

creamy-potato-29402 · Answer

Very unpleasant as there is no real way to debug it except to read code and guess

fresh-umbrella-15520 · Answer

exactly I was googling the error but it wasn t much help