ACK IAM :: Blue Green deployment

[transadm312]

Describe the bug I have a requirement to deploy ACK IAM resources in secondary cluster / Blue Green deployment of EKS

Steps to reproduce Install ACK Resources in Primary Cluster Create EKS Secondary Cluster Install ACK Resources in Secondary Cluster

Expected outcome Role should be created / Updated but getting "Resource already exists" exception

Environment

• Kubernetes version - 1.21
• Using EKS (yes/no), if so version? Yes
• AWS service targeted (S3, RDS, etc.) IAM

[a-hilaly]

Hey @transadm312 , having two clusters managing the same resource is not different from having two controllers in the same cluster. I think that ideally you should use a different AWS account for the secondary cluster (Second controller), or try to use a different AWS region in the secondary cluster.

[vijtrip2]

Hi @transadm312, this looks similar to https://github.com/aws-controllers-k8s/community/issues/1381 . It is on our radar.

[eks-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle stale

[eks-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle rotten

[a-hilaly]

/lifecycle frozen