[Bug] Trouble installing cilium Network on the EKS CLUSTER without the addons

[A-LPHARM]

I'm trying out the new feature to install the Cilium network on an EKS cluster deployment without the default addons. After creating the cluster without the nodes by running the following command, I faced issues when attempting to create a node.

apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig

metadata:
  name: henry-eks-app
  region: us-east-1

addonsConfig:
  disableDefaultAddons: true

EKSCTL Version:

eksctl version: 0.185.0

Cilium Installation Command:

helm install cilium cilium/cilium --version 1.15.6 \
  --namespace kube-system \
  --set eni.enabled=true \
  --set ipam.mode=eni \
  --set egressMasqueradeInterfaces=eth0 \
  --set routingMode=native

Node Group Configuration:

apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig

metadata:
  name: henry-eks
  region: us-east-1

managedNodeGroups:
  - name: henry-eks-app
    instanceType: t2.medium
    desiredCapacity: 1
    privateNetworking: true

Logs:

2024-07-12 21:29:39 [ℹ]  1 nodegroup (henry-eks-app) was included (based on the include/exclude rules)
2024-07-12 21:29:39 [ℹ]  will create a CloudFormation stack for each of 1 managed nodegroups in cluster "henry-eks-app"
2024-07-12 21:29:39 [!]  "aws-node" was not found
2024-07-12 21:29:39 [ℹ]  
2 sequential tasks: { fix cluster compatibility, 1 task: { 1 task: { create managed nodegroup "henry-eks-app" } }
}
2024-07-12 21:29:39 [ℹ]  checking cluster stack for missing resources
2024-07-12 21:29:41 [ℹ]  cluster stack has all required resources
2024-07-12 21:29:42 [ℹ]  building managed nodegroup stack "eksctl-henry-eks-app-nodegroup-henry-eks-app"
2024-07-12 21:29:43 [ℹ]  deploying stack "eksctl-henry-eks-app-nodegroup-henry-eks-app"
2024-07-12 21:29:43 [ℹ]  waiting for CloudFormation stack "eksctl-henry-eks-app-nodegroup-henry-eks-app"
2024-07-12 21:30:24 [ℹ]  waiting for CloudFormation stack "eksctl-henry-eks-app-nodegroup-henry-eks-app"
2024-07-12 21:30:58 [ℹ]  waiting for CloudFormation stack "eksctl-henry-eks-app-nodegroup-henry-eks-app"

Additional Logs:

Lease:
  HolderIdentity:  ip-192-168-70-103.ec2.internal
  AcquireTime:     <unset>
  RenewTime:       Fri, 12 Jul 2024 21:09:59 +0100
Conditions:
  Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason
 Message
  ----             ------  -----------------                 ------------------                ------
 -------
  MemoryPressure   False   Fri, 12 Jul 2024 21:08:37 +0100   Fri, 12 Jul 2024 20:57:51 +0100   KubeletHasSufficientMemory  
 kubelet has sufficient memory available
  DiskPressure     False   Fri, 12 Jul 2024 21:08:37 +0100   Fri, 12 Jul 2024 20:57:51 +0100   KubeletHasNoDiskPressure    
 kubelet has no disk pressure
  PIDPressure      False   Fri, 12 Jul 2024 21:08:37 +0100   Fri, 12 Jul 2024 20:57:51 +0100   KubeletHasSufficientPID     
 kubelet has sufficient PID available
  Ready            False   Fri, 12 Jul 2024 21:08:37 +0100   Fri, 12 Jul 2024 20:57:51 +0100   KubeletNotReady
 container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized

Issue:

The logs indicate that the aws-node daemonset was not found, and the CNI plugin was not initialized, resulting in the failure to create the node.

1. Created the cluster without nodes.
2. Installed Cilium as the CNI plugin.
3. Attempted to create a node group, which failed.

Any advice or solutions would be greatly appreciated!

[github-actions]

Hello A-LPHARM 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.