Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resiliency: Traffic ingress health checks should be configured #550

Open
niallthomson opened this issue Jul 23, 2024 · 0 comments
Open

Resiliency: Traffic ingress health checks should be configured #550

niallthomson opened this issue Jul 23, 2024 · 0 comments
Assignees
Labels
idea New best practices idea

Comments

@niallthomson
Copy link
Contributor

Is your idea request related to a problem that you've solved? Please describe.
Customer operating workloads on EKS had an operational issue affecting worker nodes and the pods scheduled on them. Although pod health checks had been configured there was not appropriate health checks configured on the ingress routing traffic to these pods, resulting in persistent 504 errors until the pods were evicted (5+ minutes). If health checks had been configured at the traffic ingress level then the pods would have been marked as unhealthy targets and removed from the pool.

Describe the best practice
When using an Ingress or Service of type LoadBalancer appropriate health checks should be configured so that the load balancer can perform its own checks of the health of its targets. For example with the AWS Load Balancer Controller the health check annotations for Ingress or Service can be leveraged to ensure the respective ALB or NLB is perform health checks of the targets independent of the Kubernetes probes.

Describe alternatives you've considered
N/A

Additional context
N/A

@niallthomson niallthomson added the idea New best practices idea label Jul 23, 2024
@svennam92 svennam92 assigned Tim-AWS and unassigned jicowan Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
idea New best practices idea
Projects
None yet
Development

No branches or pull requests

3 participants