You can find Kubernetes API server metrics here. You can use Tutorial for Adding a New Prometheus Scrape Target: Prometheus KPI Server Metrics to collect metrics and create CloudWatch dashboard to monitor your cluster’s control plane. So you can also use Amazon CloudWatch to monitor the EKS control plane. In May 2020, CloudWatch added support for monitoring Prometheus metrics in CloudWatch Container Insights. You can use Prometheus to collect and store these metrics. These metrics are represented in a Prometheus text format. You can view the metrics exposed using kubectl: Kubernetes exposes control plane metrics at the /metrics endpoint. ![]() For example, poorly written controllers can overload the API servers, affecting your application's availability. An unhealthy control plane can compromise the availability of the workloads running inside the cluster. Monitoring Kubernetes API metrics can give you insights into control plane performance and identify issues. Recommendations ¶ Monitor Control Plane Metrics ¶ Whether users and worker nodes connect to the API server using the public endpoint or the EKS-managed ENI, there are redundant paths for connection. You can configure whether your Kubernetes cluster’s API server is reachable from the public internet (using the public endpoint) or through your VPC (using the EKS-managed ENIs) or both. EKS also provisions two ENIs in different AZs to facilitate communication to your worker nodes. The managed endpoint uses NLB to load balance Kubernetes API servers. When you create a new cluster, Amazon EKS creates a highly-available endpoint for the managed Kubernetes API server that you use to communicate with your cluster (using tools like kubectl). This architecture ensures that an event in a single AZ doesn’t affect the EKS cluster's availability. EKS runs a NAT Gateway in each AZ, and API servers and etcd servers run in a private subnet. Likewise, for durability, the etcd server nodes also run in an auto-scaling group that spans three AZs. EKS runs a minimum of two API server nodes in distinct Availability Zones (AZs) within in AWS region. Kubernetes API server nodes that run components like the API server, scheduler, and kube-controller-manager run in an auto-scaling group. ![]() The EKS control plane comprises the Kubernetes API server nodes, etcd cluster. The Kubernetes control plane managed by EKS runs inside an EKS managed VPC. EKS Architecture ¶ĮKS architecture is designed to eliminate any single points of failure that may compromise the availability and durability of the Kubernetes control plane. Existing applications running on upstream Kubernetes are compatible with Amazon EKS.ĮKS automatically manages the availability and scalability of the Kubernetes control plane nodes, and it automatically replaces unhealthy control plane nodes. This conformance ensures that EKS supports the Kubernetes APIs, just like the open-source community version that you can install on EC2 or on-premises. It runs upstream Kubernetes and is certified Kubernetes conformant. Monitoring for Network performance issuesĪmazon Elastic Kubernetes Service (EKS) is a managed Kubernetes service that makes it easy for you to run Kubernetes on AWS without needing to install, operate, and maintain your own Kubernetes control plane or worker nodes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |