EKS Addon Create Failing - "Addon Already Exists"

[t-margheim]

Summary

During the kubernetes step, Pulumi attempts to create an EKS Addon that already exists in AWS, resulting in a ResourceInUseException. The Pulumi state appears out of sync with the actual AWS resources, and running --refresh does not detect the existing addon.

Context

• Step: kubernetes
• Resource: aws:eks/addon:Addon (aws-ebs-csi-driver)
• Error: ResourceInUseException: Addon already exists

Error Details

error: creating EKS Add-On (example-workload-20251029:aws-ebs-csi-driver):
operation error EKS: CreateAddon, https response error StatusCode: 409,
RequestID: e45a1a2b-22bb-4c71-a7c0-12b230741f1f,
ResourceInUseException: Addon already exists.

Resource Configuration

URN: urn:pulumi:example-workload::ptd-aws-workload-eks::ptd:AWSWorkloadEKS$ptd:AWSEKSCluster$aws:eks/cluster:Cluster$aws:eks/addon:Addon::example-workload-20251029-ebs-csi
Addon Name: aws-ebs-csi-driver
Addon Version: v1.41.0-eksbuild.1
Cluster Name: example-workload-20251029

Problem

1. The EKS addon exists in AWS but is not tracked in Pulumi state
2. pulumi refresh does not detect the existing addon
3. Pulumi attempts to create the addon, which fails because it already exists
4. The state is out of sync with reality

Related Discussion

Discussed in an internal Slack conversation.

Next Steps

Determine the best path forward based on:

• Whether this is a one-time migration issue or will recur
• Impact of deleting and recreating the addon
• Whether other addons are affected

[ian-flores]

This should be resolved by PR #114, which adds proper dependency ordering between the EBS CSI addon and StorageClassPatch. The root cause was that StorageClassPatch could run before the addon was ready, causing deployment failures that left Pulumi state out of sync with AWS.