Skip to content

Conversation

@ppippi-dev
Copy link
Contributor

Summary

  • Add optional ServiceAccount configuration for cloud IAM integration (AWS IRSA, GCP Workload Identity)
  • Disabled by default (serviceAccount.create: false) to maintain backward compatibility
  • Applied to all Deployments and Jobs in the chart

Changes

File Description
values.yaml Add serviceAccount section with create, name, annotations, automountServiceAccountToken
_helpers.tpl Add mcp-stack.serviceAccountName helper function
serviceaccount.yaml New ServiceAccount template (created only when create: true)
values.schema.json Add schema validation for serviceAccount
7 Deployments Add serviceAccountName reference
3 Jobs Add serviceAccountName reference

Usage Example

serviceAccount:
  create: true
  name: "my-custom-sa"
  annotations:
    eks.amazonaws.com/role-arn: arn:aws:iam::123456789:role/my-role

Validation

  • helm lint passes
  • helm template renders correctly with default values
  • helm template --set serviceAccount.create=true creates ServiceAccount resource

Add optional ServiceAccount configuration for cloud IAM integration
(AWS IRSA, GCP Workload Identity). Disabled by default to maintain
backward compatibility.

- Add serviceAccount section to values.yaml
- Add serviceAccountName helper to _helpers.tpl
- Create serviceaccount.yaml template
- Attach serviceAccountName to all Deployments and Jobs
- Add schema validation in values.schema.json

Signed-off-by: ppippi-dev <[email protected]>
@ppippi-dev ppippi-dev force-pushed the feature/helm-serviceaccount-support branch from 4df2b8a to c861fdf Compare December 24, 2025 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant