[Bug] update-aws-node breaks aws-node daemonset #6048
Description
What were you trying to accomplish?
Update aws-node using eksctl utils update-aws-node
What happened?
aws-node pods are unable to start:
NAME READY STATUS RESTARTS AGE
aws-node-8gtcl 0/1 CreateContainerConfigError 0 5s
It is configured to run as non-root, but the image will run as root:
Error: container has runAsNonRoot and image will run as root (pod: "aws-node-8gtcl_kube-system(0b5691cd-dca7-40f1-af36-d232baf1c155)", container: aws-node)
How to reproduce it?
Install eksctl version 0.122.0 and run:
eksctl utils update-aws-node --cluster <cluster name> --approve
Logs
eksctl utils update-aws-node --cluster <cluster name> --approve
2022-12-12 16:19:04 [ℹ] skipped existing "kube-system:ServiceAccount/aws-node"
2022-12-12 16:19:04 [ℹ] replaced "CustomResourceDefinition.apiextensions.k8s.io/eniconfigs.crd.k8s.amazonaws.com"
2022-12-12 16:19:04 [ℹ] replaced "ClusterRole.rbac.authorization.k8s.io/aws-node"
2022-12-12 16:19:04 [ℹ] replaced "ClusterRoleBinding.rbac.authorization.k8s.io/aws-node"
2022-12-12 16:19:05 [ℹ] replaced "kube-system:DaemonSet.apps/aws-node"
2022-12-12 16:19:05 [ℹ] "aws-node" is now up-to-date
Anything else we need to know?
Using Mac OS with downloaded binary.
Versions
$ eksctl info
eksctl version: 0.122.0
kubectl version: v1.26.0
OS: darwin