Skip to content

Investigate if the built-in CNI driver in EKS can be deleted (and update docs accordingly) #10420

@errordeveloper

Description

@errordeveloper

Right now we instruct the user to disable built-in VPC CNI driver by running the following command:

kubectl -n kube-system set image daemonset/aws-node aws-node=docker.io/spaster/alpine-sleep

This is an effective solution, however conceptually it may seem a little odd to the user. Also, if user follows EKS upgrade instructions without knowing that this was done at some stage earlier, they will put the VPC CNI driver back and break Cilium.

Metadata

Metadata

Labels

area/documentationImpacts the documentation, including textual changes, sphinx, or other doc generation code.area/eniImpacts ENI based IPAM.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions