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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support custom name for serviceAccount in helm chart #529

Open
kerruba-milkman opened this issue Dec 7, 2023 · 1 comment 路 May be fixed by #530
Open

Support custom name for serviceAccount in helm chart #529

kerruba-milkman opened this issue Dec 7, 2023 · 1 comment 路 May be fixed by #530
Labels
good-first-issue Start here if you'd like to start contributing to Pulumi impact/usability Something that impacts users' ability to use the product easily and intuitively kind/enhancement Improvements or new features

Comments

@kerruba-milkman
Copy link

Hello!

  • Vote on this issue by adding a 馃憤 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Currently the helm chart uses the helper pulumi-kubernetes-operator.fullname to populate the service account name, but the values.yaml file provide a serviceAccount.name value that is only used if the serviceAccount.create is false.

Could make sense to use the serviceAccount.name field as .metadata.name in the ServiceAccount and fallback to the fullname only if the serviceAccount.name field is empty or missing.

Having to use the fullnameOverride value to override the name of the serviceAccount doesn't provide enought flexibility and it could be confusing having both serviceAccount.create = true and serviceAccount.name = "non-empty-string".

@kerruba-milkman kerruba-milkman added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Dec 7, 2023
@mjeffryes mjeffryes added impact/usability Something that impacts users' ability to use the product easily and intuitively good-first-issue Start here if you'd like to start contributing to Pulumi labels Dec 8, 2023
@mjeffryes
Copy link
Contributor

Thanks for reporting this @kerruba-milkman, I'll add it to our backlog.

@mjeffryes mjeffryes removed the needs-triage Needs attention from the triage team label Dec 9, 2023
@ishuar ishuar linked a pull request Dec 12, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good-first-issue Start here if you'd like to start contributing to Pulumi impact/usability Something that impacts users' ability to use the product easily and intuitively kind/enhancement Improvements or new features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants