Amazon EKS now surfaces cluster health status details
Amazon Elastic Kubernetes Service (EKS) now surfaces cluster-related health issues in the EKS console and API, providing administrators enhanced visibility into the health of their clusters. Cluster health status information helps customers to quickly diagnose, troubleshoot, and remedy issues with their clusters, enabling them to run more up-to-date and secure application environments.
Amazon Elastic Kubernetes Service (EKS) now surfaces cluster-related health issues in the EKS console and API, providing administrators enhanced visibility into the health of their clusters. Cluster health status information helps customers to quickly diagnose, troubleshoot, and remedy issues with their clusters, enabling them to run more up-to-date and secure application environments.
The health of an EKS cluster is a shared responsibility between AWS and customers, who are responsible for configuring cluster infrastructure such as IAM roles and EC2 subnets. Underlying infrastructure or configuration issues may lead to impaired EKS clusters and prevent EKS from applying updates or prevent customers from upgrading to newer Kubernetes versions. EKS cluster health issues now surface detailed reason codes and descriptions on how to resolve issues. This reduces the time administrators need to spend troubleshooting infrastructure health issues, making it easier to run secure Kubernetes environments.
Customers can view cluster health status for any new or existing cluster using the AWS Console, CLI, and language SDKs in all AWS Regions where EKS is available. To learn more, including details about status codes and resolutions, see the EKS documentation.