AWS eks documentation change
Summary
Added a markdown link to view the page in markdown format and fixed a typo (changed 'in in' to 'in an')
Security assessment
The change adds a markdown link for viewing the page and corrects a grammatical error. No security content was added or modified, and the typo fix does not address any security issue.
Diff
diff --git a/eks/latest/best-practices/control-plane.md b/eks/latest/best-practices/control-plane.md index 702a9d749..ee817e9d0 100644 --- a//eks/latest/best-practices/control-plane.md +++ b//eks/latest/best-practices/control-plane.md @@ -0,0 +1,2 @@ +[View a markdown version of this page](control-plane.md) + @@ -21 +23 @@ EKS architecture is designed to eliminate any single points of failure that may -The Kubernetes control plane managed by EKS runs inside an EKS managed VPC. The EKS control plane comprises the Kubernetes API server nodes, etcd cluster. Kubernetes API server nodes that run components like the API server, scheduler, and `kube-controller-manager` run in an auto-scaling group. EKS runs a minimum of two API server nodes in distinct Availability Zones (AZs) within in AWS region. Likewise, for durability, the etcd server nodes also run in an auto-scaling group that spans three AZs. EKS runs a NAT Gateway in each AZ, and API servers and etcd servers run in a private subnet. This architecture ensures that an event in a single AZ doesn’t affect the EKS cluster’s availability. +The Kubernetes control plane managed by EKS runs inside an EKS managed VPC. The EKS control plane comprises the Kubernetes API server nodes, etcd cluster. Kubernetes API server nodes that run components like the API server, scheduler, and `kube-controller-manager` run in an auto-scaling group. EKS runs a minimum of two API server nodes in distinct Availability Zones (AZs) within an AWS region. Likewise, for durability, the etcd server nodes also run in an auto-scaling group that spans three AZs. EKS runs a NAT Gateway in each AZ, and API servers and etcd servers run in a private subnet. This architecture ensures that an event in a single AZ doesn’t affect the EKS cluster’s availability.