跳至內容

EKS multi subnet communication

0

Hello, I would like to deploy an EKS cluster on private and public in order to expose some services to internet. In my organisation, communication between components in private subnets and public one are managed by firewall rules. If I deploy my cluster and nodes to private subnet everything is ok but if I add public subnet to my control plan for being able to deploy ALB then EKS change nodes status to unknown. I guess it's because communication between private and public subnets are blocked by my internal firewall. In order to create firewall request , i would like to know what are the network traffic I need to allow between subnet for having ready nodes status ? Rgds.

已提問 2 年前檢視次數 650 次
2 個答案
0

Basically you need to check logs(Kubelet) and communication between worker nodes and control plane. This is reason that cause the node in node ready state.

Please check following guides to troubleshoot this issues.

https://repost.aws/knowledge-center/eks-worker-node-not-ready

https://repost.aws/knowledge-center/eks-node-status-ready

AWS
已回答 2 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。