Summary
Users on version 0.63.4 deploying with Helm charts and customizing serviceAccount.create in values.yaml are experiencing issues with new pods losing permission to the Kubernetes API when Rolebinding is deployed. Editing the Rolebinding to add the ‘default’ service account and restarting the new workload pods resolves the problem.
Question
Hi guys!
Anyone on 0.63.4 that:
• deploys with helm charts
• customizes the “serviceAccount.create” on values.yaml
is noticing that the new pods “lose permission” to the kubernetes API when the Rolebinding is deployed?
somehow I always have to edit the rolebinding to add the “default” service account and restart the new workload pods
have checked and the deployments bind the correct service account
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.