fix: Set IRSA service account in EKS Fargate pattern #2081
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Motivation and Context
Current EKS Fargate pattern doesn't explicitly set the IRSA service account. However, it assumes the namespace and service account name are both
karpenter
when not provided. This causes failure if the user deploys to different namespace or use different helm release name.This commit resolves this by explicitly setting
irsa_namespace_service_accounts
with the namespace and service account name variable to ensure correct IRSA configuration.How was this change tested?
pre-commit run -a
with this PRAdditional Notes