Skip to content

Helm chart should allow conditionally creating the service accounts #6250

Description

@mycodeself

Pre-submission checklist

  • I have searched existing issues and confirmed this is not a duplicate.
  • I understand that submitting a feature request does not guarantee it will be implemented.

Proposed Feature

The helm chart should support the standard pattern used by most of other helm charts to conditionally disable the creation of the services accounts, specially the one for the controller which might require the role ARN annotation and as a user I would like to create it dynamically to avoid hardcoding a role ARN in the values.yaml file.

controller:
  serviceAccount:
    create: false           # when false, chart does NOT render the SA manifest

This requires a simple change in the service account template here

{{- if and .Values.controller.enabled .Values.controller.serviceAccount.create }}
apiVersion: v1
kind: ServiceAccount
metadata:

I would be open contributing to apply this changes.

Motivation and Use Case

In IRSA setups the ServiceAccount could be created outside the helm chart in a dynamic way with the correct eks.amazonaws.com/role-arn annotation without having to actually hardcode the role ARN. The Helm chart should only consume that SA, not own it.

Alternatives Considered

No response

Metadata

Metadata

Assignees

Labels

kind/enhancementAn entirely new featurekind/proposalIndicates maintainers have not yet committed to a feature requestneeds/areaIssue or PR needs to be labeled to indicate what parts of the code base are affectedneeds/priorityPriority has not yet been determined; a good signal that maintainers aren't fully committed

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions