You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The rollout commands currently do not use the service account's API key, so that means they are run using the credentials of the user running the deploy. This means that they will not work on CI, where the user has limited access.
To add to this, rollout is useful when just the linked ConfigMap changes, such as with a new environment variable, but not the image tag. This can be confusing when a deployment is run to update an environment variable and it appears that the deploy didn't work since the pods are still using a copy of the old secrets.
The rollout commands currently do not use the service account's API key, so that means they are run using the credentials of the user running the deploy. This means that they will not work on CI, where the user has limited access.
We should see if there is a way to run kubectl with service account creds, either with the ansible k8s role or the ansible kubectl role
The text was updated successfully, but these errors were encountered: