Healthcheck

Route53 health checks Although we have already monitoring with Prometheus in our Kubernetes cluster, we want to additionally monitor our customer systems from outside. This means that, in contrast to Prometheus monitoring, additional components for routing traffic into our Kubernetes cluster will be checked. In our AWS environment, this additional components will be checked: Route53 the Application Load Balancer the corresponding certificates at the Load Balancer Target Groups Ingress Controller in the cluster....

Loadbalancer health checks in EKS Todays post is about setting up load balancer health checks for a Kubernetes Cluster (EKS) within AWS. The setup consists of an Application Load Balancer, an Auto Scaling group and a target group which contains the Kubernetes worker nodes. The diagram shows a overview of the setup we aim for: flowchart TB ALB[Load Balancer]--Redirects traffic to-->ide1 asg[Autoscaling]--Considers ALB Health-Checks-->ALB subgraph ide1 [Target-Group] hs[Health-Check]--Port-30003-->n1 hs[Health-Check]--Port-30003-->n2 n1[EKS-Node-1]-->POD-echo-server-1 n2[EKS-Node-2]-->POD-echo-server-2 end The health checks configured in the target group did not work with the default configuration and reported unhealthy....