Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Pods still use default service account even if serviceAccount.create is true in the helm chart #370

Closed
ericwyles opened this issue Sep 5, 2024 · 0 comments · Fixed by #371
Labels
bug Something isn't working

Comments

@ericwyles
Copy link
Contributor

What steps did you take and what happened:

Deploy archivista using helm. Include this snippet in values to create a custom service account:

serviceAccount:
  create: true
  annotations: {}
  name: eric-was-here

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants