-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[Bug] Creating ArgoCD Capabilities Ignores RoleArn Designation and Creates new Role #8654
Copy link
Copy link
Closed
Labels
Description
What were you trying to accomplish?
I followed the instructions on https://docs.aws.amazon.com/eks/latest/userguide/argocd-create-eksctl.html to create the capability. It said to create a new role and then specify the role in the yaml file sent to the eksctl create capability.. command.
What happened?
The result of the action was two cloudformation templates being deployed. The first one created a new role, and then second one created the capability, referencing the role created by the first CFN template. The role. I specified in my capability yaml was complete ignored.
How to reproduce it?
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
name: auto-mode-demo
region: us-west-2
capabilities:
- name: my-argocd
type: ARGOCD
roleArn: arn:aws:iam::REDACTED:role/ArgoCDCapabilityRole
deletePropagationPolicy: RETAIN
configuration:
argocd:
awsIdc:
idcInstanceArn: arn:aws:sso:::instance/ssoins-REDACTED
idcRegion: us-east-1
rbacRoleMappings:
- role: ADMIN
identities:
- id: REDACTED
type: SSO_USEReksctl create capability -f argocd-capability.yamlLogs
2026-01-22 18:51:48 [ℹ] creating capability my-argocd
2026-01-22 18:51:50 [ℹ] deploying stack "eksctl-auto-mode-demo-capability-role-REDACTED"
2026-01-22 18:51:51 [ℹ] waiting for CloudFormation stack "eksctl-auto-mode-demo-capability-role-REDACTED"
2026-01-22 18:52:21 [ℹ] waiting for CloudFormation stack "eksctl-auto-mode-demo-capability-role-REDACTED"
2026-01-22 18:52:21 [ℹ] deploying stack "eksctl-auto-mode-demo-capability-REDACTED"
2026-01-22 18:52:21 [ℹ] waiting for CloudFormation stack "eksctl-auto-mode-demo-capability-REDACTED"Info
$ eksctl info
eksctl version: 0.221.0-dev+de9424a29.2025-12-25T08:22:07Z
kubectl version: v1.30.1
OS: darwin
Reactions are currently unavailable