CoreDNS Addon gets created if Cluster is in AutoMode

[nis-thac]

Describe what happened

When creating a Cluster with AutoMode enabled, Pulumi tries to create the CoreDNS Addon by default, and fails. The CoreDNS Addon cannot be added to a AutoMode Cluster, as per the documentation.

This can be fixed by setting:

corednsAddonOptions: {
    enabled: false,
},

but this option should be set by Pulumi automatically when creating an AutoMode Cluster.

Sample program

import * as eks from '@pulumi/eks';

new eks.Cluster("sample-cluster", {
    [...]
    autoMode: {
        enabled: true,
        [...]
    },
});

Log output

No response

Affected Resource(s)

Cluster if AutoMode is enabled.

Output of pulumi about

CLI
Version 3.159.0
Go Version go1.24.1
Go Compiler gc

Plugins
KIND NAME VERSION
language nodejs 3.159.0

Host
OS Microsoft Windows 10 Pro
Version 10.0.19045 Build 19045
Arch x86_64

This project is written in nodejs: executable='C:\Program Files\nodejs\node.exe' version='v18.20.5'

Backend is S3.

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[rquitales]

Thanks for reporting this issue!

[flostadler]

The coredns addon should not be added to the cluster by default if auto mode is enabled:

pulumi-eks/nodejs/eks/cluster/cluster.ts

Lines 1171 to 1175 in 0658ec1

	if (
	corednsExplicitlyEnabled ||
	((fargate || !args.skipDefaultNodeGroup || args.autoMode?.enabled) &&
	(args.corednsAddonOptions?.enabled ?? true))
	) {

This example with auto mode deploys successfully for me and doesn't add the coredns addon: https://github.com/pulumi/pulumi-eks/blob/master/examples/eks-auto-mode/index.ts

@nis-thac Could you please provide us with a self contained repro of this problem and run pulumi about in the context of your pulumi program so we can see what versions you're using?

[dirien]

@flostadler: Just stumbled over the same issue.

const cluster = new eks.Cluster("eks-auto-mode", {
    name: clusterName,
    // EKS Auto Mode requires Access Entries, use either the `Api` or `ApiAndConfigMap` authentication mode.
    authenticationMode: eks.AuthenticationMode.Api,
    vpcId: eksVpc.vpcId,
    publicSubnetIds: eksVpc.publicSubnetIds,
    privateSubnetIds: eksVpc.privateSubnetIds,
    // Enables compute, storage and load balancing for the cluster.
    autoMode: {
        enabled: true,
    }
});

I use version @pulumi/eks": "4.0.1" and this is the output of my pulumi up? run:

 +      │  └─ aws:iam:RolePolicyAttachment         eks-auto-mode-eksRole-1587f79c              created (2s)        
 +      ├─ aws:iam:InstanceProfile                 eks-auto-mode-instanceProfile               created (8s)        
 +      ├─ aws:eks:Cluster                         eks-auto-mode-eksCluster                    created (564s)      
 +      ├─ aws:eks:AccessEntry                     eks-auto-mode-defaultNodeGroupInstanceRole  created (1s)        
 +      ├─ pulumi:providers:kubernetes             eks-auto-mode-eks-k8s                       created (0.28s)     
 +      └─ aws:eks:Addon                           eks-auto-mode-coredns                       created (919s)      

I reopened this issue to follow up on this.