Skip to content

fix: fargate profile for duplicate zone when add multiple subnets #177

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jun 6, 2025
Merged

fix: fargate profile for duplicate zone when add multiple subnets #177

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions fargate_profile.tf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,11 @@ locals {

fargate_namespaces = concat(local.essentials_namespaces, local.kube_system_namespaces)

subnets_by_az = {
for subnet_id in var.subnet_ids :
data.aws_subnet.subnets[subnet_id].availability_zone => subnet_id...
}

default_fargate_profiles = merge(
{
essentials = {
Expand All @@ -16,14 +21,14 @@ locals {
]
}
},
{ for subnet in var.subnet_ids :
"kube-system-${substr(data.aws_subnet.subnets[subnet].availability_zone, -2, -1)}" => {
iam_role_name = "fargate_profile_${substr(data.aws_subnet.subnets[subnet].availability_zone, -2, -1)}"
{ for az, az_subnets in local.subnets_by_az :
"kube-system-${substr(az, -2, 2)}" => {
iam_role_name = "fargate_profile_${substr(az, -2, 2)}"
selectors = [
{ namespace = "kube-system" }
]
# Create one profile per AZ for even spread
subnet_ids = [subnet]
subnet_ids = az_subnets
}
},
)
Expand Down
Loading