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
When using kubernetes workload identity service account, there is no credentials file mounted in the container, however there is the option to mount the service account token: automountServiceAccountToken. This looks like a JWT belonging to the application's workload identity service account.
It therefore seems possible to have the option to use this JWT directly instead of constructing one from the credentials file.
Does this seem plausible to you?
The text was updated successfully, but these errors were encountered:
After digging some more I have found the correct way to authenticate using workload identity, which is to retrieve the token from the metadata server. See PR.
When using kubernetes workload identity service account, there is no credentials file mounted in the container, however there is the option to mount the service account token:
automountServiceAccountToken
. This looks like a JWT belonging to the application's workload identity service account.It therefore seems possible to have the option to use this JWT directly instead of constructing one from the credentials file.
Does this seem plausible to you?
The text was updated successfully, but these errors were encountered: