Allow disabling the default CNI

[jaxxstorm]

It is currently not possible to disable the default CNI in the cluster.

I had expected that removing the CNI addon would be enough, but the CNI daemonset is still created.

We should have a top level parameter/option that disables the default CNI being installed and removes all default configuration for it

[rquitales]

It looks like the CNI manifests for the daemonset etc is always applied:

pulumi-eks/nodejs/eks/cmd/provider/cni.ts

Line 233 in 7febe52

const yamlPath = path.join(__dirname, "../../cni/aws-k8s-cni.yaml");

We should improve this logic to only apply it when necessary.

[PavelGloba]

Any news about it?

[DavidJFelix]

@PavelGloba

Any news about it?

I think this is possible using defaultAddonsToRemove.

const cluster = new eks.Cluster('example',  {
  // ...
  defaultAddonsToRemove: ['vpc-cni'],
  // ...
})

But I haven't tried this.

[PavelGloba]

@DavidJFelix

@PavelGloba

Any news about it?

I think this is possible using defaultAddonsToRemove.

const cluster = new eks.Cluster('example',  {
  // ...
  defaultAddonsToRemove: ['vpc-cni'],
  // ...
})

But I haven't tried this.

This issue was created because of the conversation in the chat, where this option didn't actually work for the cni. So I'm not sure if it was fixed