- 最新
- 投票最多
- 评论最多
Hello, Greetings!
- To understand the health check issues with the load balancer in your Amazon EKS, the below pointers could be considered for troubleshooting as the health check on the load balancer could fail due to multiple/any of the below reason.
Check the status of the pod
Check the pod and service label selectors
Check for missing endpoints
Check the service traffic policy and cluster security groups for Application Load Balancers
Verify that your EKS is configured for targetPort
Verify that your AWS Load Balancer Controller has the correct permissions
Check the ingress annotations for issues with Application Load Balancers
Check the Kubernetes Service annotations for issues with Network Load Balancers
Manually test a health check
Check the networking
Restart the kube-proxy
-
The detailed resolution for the above provided pointers could be found in this document [1]
-
Also Unhealthy targets/ failed healthchecks in the Application Load Balancer target groups happen for two reasons. Either the service traffic policy, spec.externalTrafficPolicy, is set to Local instead of Cluster. Or, the node groups in a cluster have different cluster security groups associated with them, and traffic cannot flow freely between the node groups.
> Verify that the traffic policy is correctly configured: $ kubectl get svc SERVICE_NAME -n YOUR_NAMESPACE -o=jsonpath='{.spec.externalTrafficPolicy}{"\n"}' Example output: Local > Change the setting to Cluster: $ kubectl edit svc SERVICE_NAME -n YOUR_NAMESPACE
In most cases, performing the above checks helps to identify the issue.
You can also follow the steps in this documentation[1] to troubleshoot the above mentioned pointers.
Thank you!
References : [1] https://repost.aws/knowledge-center/eks-resolve-failed-health-check-alb-nlb
相关内容
- AWS 官方已更新 4 个月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前