- Newest
- Most votes
- Most comments
CNI Plugin Compatibility:
Double-check the specific CNI plugin version you installed for compatibility with Kubernetes 1.30. While you mentioned installing the CNI plugin, ensure it's the recommended version for your current Kubernetes distribution. Refer to the official AWS documentation for known compatible versions:
https://docs.aws.amazon.com/eks/latest/userguide/managing-vpc-cni.html
kube-proxy Verification:
Verify that kube-proxy is running correctly on each node. You can use the following kubectl command to check its pod status:
kubectl get pods -n kube-system | grep kube-proxy
Network Connectivity:
Re-evaluate network connectivity between the control plane and the nodes. Security groups might have inadvertently blocked port 50051 after the upgrade. Ensure inbound traffic on port 50051 from the control plane to the nodes is explicitly allowed
For more please follow the link https://aws.amazon.com/about-aws/whats-new/2023/12/amazon-eks-surfaces-cluster-health-status-details/
Relevant content
- asked 6 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
