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
It seems that automount_service_account_token defaults to false on a deployment with no knob to change it. Doesn't this render the same knob useless on a service account since the deployment setting takes precedence? Is there a compelling reason that this knob does not exist for a deployment?
The text was updated successfully, but these errors were encountered:
I see the explanation is referencing the default service account which is not my use case, but the reasoning isn't entirely clear. Something about ambiguity, it seems. Adding a blurb to the deployment documentation may reduce the issue volume surrounding this feature omission. Otherwise, peeps are left to assume that this is a bug or oversight. Something such as automount_service_account_token (not implemented) with reasoning and a link to the workaround.
I was just about to create an issue about this too, after debugging it and realising what was happening.
This definitely needs to be in the documentation. @dolvany Would you be open to reopening this issue (to assist in discovery / a pointer to update the documentation)?
ghost
locked and limited conversation to collaborators
Apr 21, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It seems that automount_service_account_token defaults to false on a deployment with no knob to change it. Doesn't this render the same knob useless on a service account since the deployment setting takes precedence? Is there a compelling reason that this knob does not exist for a deployment?
The text was updated successfully, but these errors were encountered: