What feature/behavior/change do you want?
With current design, the inline policy name will always be Policy1. For example, if user define ClusterConfig as follow,
addons:
- name: vpc-cni
version: latest
podIdentityAssociations:
- namespace: kube-system
serviceAccountName: aws-node
# Copied from https://docs.aws.amazon.com/eks/latest/userguide/cni-iam-role.html#cni-iam-role-create-ipv6-policy
permissionPolicy:
Version: "2012-10-17"
Statement:
- Effect: Allow
Action:
- "ec2:AssignIpv6Addresses"
- "ec2:DescribeInstances"
- "ec2:DescribeTags"
- "ec2:DescribeNetworkInterfaces"
- "ec2:DescribeInstanceTypes"
Resource: '*'
- Effect: Allow
Action:
- "ec2:CreateTags"
Resource: 'arn:aws:ec2:*:*:network-interface/*'
It would get
Because inside the code, it hard-coded as Policy1
|
if len(rs.attachPolicy) != 0 { |
|
rs.template.AttachPolicy("Policy1", roleRef, rs.attachPolicy) |
|
} |
Why do you want this feature?
Allow user to define the inline policy name (or custom defined suffix/prefix).
What feature/behavior/change do you want?
With current design, the inline policy name will always be
Policy1. For example, if user define ClusterConfig as follow,It would get
Because inside the code, it hard-coded as
Policy1eksctl/pkg/cfn/builder/iam.go
Lines 514 to 516 in ace3ad1
Why do you want this feature?
Allow user to define the inline policy name (or custom defined suffix/prefix).