<p>Ensure the API server endpoint access is both Private and Public to ensure the pods are reachable from the control Plane</p>

CC BY-SA 4.0
2024-11-06T12:55:30.280Z
2024-11-06T12:55:30.280Z
madhinigm
<p>I'm currently facing an issue with my Kubernetes cluster where all the aws-node pods in the kube-system namespace are in a CrashLoopBackOff state. Here are the details of my setup:</p>
<pre><code>Kubernetes Version: v1.23.17 (EKS)
Cloud Provider: AWS
CNI Plugin: AWS VPC CNI
</code></pre>
<p>Observations:</p>
<p>The aws-node pods are crashing repeatedly.
Other pods in the cluster are experiencing network connectivity issues, as they rely on the aws-node pods for networking.
I have checked the logs of the aws-node pods, but I’m unable to identify the specific cause of the crashes.</p>

<kubernetes><amazon-web-services><networking><eks><aws-vpc>
why all my aws-node Pods in CrashLoopBackOff State in Kubernetes Cluster
Sudhanshu Sinha
# why all my aws-node Pods in CrashLoopBackOff State in Kubernetes Cluster

(Asked by: username_0 on 2024-09-24)

I'm currently facing an issue with my Kubernetes cluster where all the aws-node pods in the kube-system namespace are in a CrashLoopBackOff state. Here are the details of my setup:
Kubernetes Version: v1.23.17 (EKS)
Cloud Provider: AWS
CNI Plugin: AWS VPC CNI

Observations:
The aws-node pods are crashing repeatedly.
Other pods in the cluster are experiencing network connectivity issues, as they rely on the aws-node pods for networking.
I have checked the logs of the aws-node pods, but I’m unable to identify the specific cause of the crashes.

**Tags:** kubernetes, amazon-web-services, networking, eks, aws-vpc


---

## 1 answers

### Answer by username_1 on 2024-11-06. Score: 0

Ensure the API server endpoint access is both Private and Public to ensure the pods are reachable from the control Plane


---

