aws-network-policy-agent is not pre-loaded in the latest AMI

[tvizor]

What happened:
aws-network-policy-agent image is not preloaded on the latest AL2 EKS optimized AMI. As per awslabs/amazon-eks-ami#938 other images are preloaded to speedup node start.

Node start times increased with the latest version of the addon.

VPC CNI Plugin events:

Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  2m4s  default-scheduler  Successfully assigned kube-system/aws-node-<redacted> to <redacted>
  Normal  Pulled     2m3s  kubelet            Container image "602401143452.dkr.ecr.us-east-1.amazonaws.com/amazon-k8s-cni-init:v1.14.0-eksbuild.3" already present on machine
  Normal  Created    114s  kubelet            Created container aws-vpc-cni-init
  Normal  Started    114s  kubelet            Started container aws-vpc-cni-init
  Normal  Pulled     71s   kubelet            Container image "602401143452.dkr.ecr.us-east-1.amazonaws.com/amazon-k8s-cni:v1.14.0-eksbuild.3" already present on machine
  Normal  Created    70s   kubelet            Created container aws-node
  Normal  Started    70s   kubelet            Started container aws-node
  Normal  Pulling    70s   kubelet            Pulling image "602401143452.dkr.ecr.us-east-1.amazonaws.com/amazon/aws-network-policy-agent:v1.0.1-eksbuild.1"
  Normal  Pulled     16s   kubelet            Successfully pulled image "602401143452.dkr.ecr.us-east-1.amazonaws.com/amazon/aws-network-policy-agent:v1.0.1-eksbuild.1" in 53.831843277s (53.83185942s including waiting)
  Normal  Created    13s   kubelet            Created container aws-eks-nodeagent

What you expected to happen:

Image aws-network-policy-agent will be preloaded on the latest AMI, as other components of AWS VPC CNI plugin.

How to reproduce it (as minimally and precisely as possible):

Start a new node. Describe newly created aws-node pod.

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version): 1.27
• CNI Version: v1.14.0-eksbuild.3
• OS (e.g: cat /etc/os-release): Amazon Linux 2
• Kernel (e.g. uname -a): 5.10.186-179.751.amzn2.x86_64

[jdn5126]

@tvizor this looks like a good issue for https://github.com/awslabs/amazon-eks-ami/issues. The VPC CNI repo does not have any control there

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[tvizor]

submitted awslabs/amazon-eks-ami#1417