Open eromanova opened 1 month ago
This issue is currently awaiting triage.
If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
/kind bug
What steps did you take and what happened: I've followed https://cluster-api-aws.sigs.k8s.io/getting-started to initialize Cluster API provider AWS on a management cluster:
clusterawsadm bootstrap iam create-cloudformation-stack
.export AWS_B64ENCODED_CREDENTIALS=$(clusterawsadm bootstrap credentials encode-as-profile)
and initialize the management cluster with AWS provider by runningclusterctl init --infrastructure aws
spec.controlPlaneLoadBalancer.loadBalancerType: nlb
What did you expect to happen: Workload cluster to deploy successfully
Anything else you would like to add: AWSCluster spec:
Should we add
elasticloadbalancing:SetSecurityGroups
role to the default cloudformation templates or did I misconfigure something? Or this is probably an expected behavior when I'm using non-default load balancer configuration I should apply custom IAM configuration as well (viaAWSIAMConfiguration
). Thanks in advance.Environment:
v2.5.0
kubectl version
):/etc/os-release
):