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 eric-was-here account is created, but the pods in the deployment still use the default account. Looking in the helm chart there is no reference to the service account name in the deployment template.
What did you expect to happen:
Pods should use the created service account.
Anything else you would like to add:
Same thing happens if you leave off the name field. An account is created named archivista but the pods don't use it.
Environment:
Archivista version: 0.5.3
The text was updated successfully, but these errors were encountered:
What steps did you take and what happened:
Deploy archivista using helm. Include this snippet in values to create a custom service account:
The
eric-was-here
account is created, but the pods in the deployment still use thedefault
account. Looking in the helm chart there is no reference to the service account name in the deployment template.What did you expect to happen:
Pods should use the created service account.
Anything else you would like to add:
Same thing happens if you leave off the
name
field. An account is created namedarchivista
but the pods don't use it.Environment:
The text was updated successfully, but these errors were encountered: