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

[Feature Request] Add Support for Service-Specific Service Accounts in Temporal Helm Chart #626

Open
seeker815 opened this issue Jan 16, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@seeker815
Copy link

seeker815 commented Jan 16, 2025

Is your feature request related to a problem? Please describe.

If we enable serviceAccount: true helm chart creates one service account for all deploys { temporal-admintools, temporal-frontend, temporal-history, temporal-matching, temporal-web, temporal-worker }

We need a way to enable service account creation and customization for each service and allow the user to set unique serviceAccount names per service.

This is an issue from security point of view and also as we use consul service mesh, it mandates using same name for service account as service name when we use ACL and setting common service account name doesn't work.

Describe the solution you'd like

we would like individual service account to be created for each of the service like so

  temporal-frontend:
    serviceAccount:
      create: true
      name: temporal-frontend
      extraAnnotations:
        
  temporal-history:
    serviceAccount:
      create: true
      name: temporal-history
      extraAnnotations:
        
  matching:
@seeker815 seeker815 added the enhancement New feature or request label Jan 16, 2025
@seeker815 seeker815 changed the title [Feature Request] FILL_TITLE_HERE [Feature Request] Add Support for Service-Specific Service Accounts in Temporal Helm Chart Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant