AWS eks documentation change
Summary
Removed detailed architecture documentation about EKS components and control plane, replacing with topic links
Security assessment
The changes involve content reorganization/removal without any security-related context. No security fixes, vulnerabilities, or security features are mentioned in the diff.
Diff
diff --git a/eks/latest/userguide/versioning.md b/eks/latest/userguide/versioning.md index 867200a62..f8b4c9c0b 100644 --- a//eks/latest/userguide/versioning.md +++ b//eks/latest/userguide/versioning.md @@ -5,2 +4,0 @@ -Cluster componentsControl plane architecture - @@ -15,23 +13 @@ This section is designed to help you learn how Kubernetes versioning operates wi -## Cluster components - -An Amazon EKS cluster consists of two primary components: the Amazon EKS control plane and Amazon EKS nodes that are registered with the control plane. - - * **Control plane** : The control plane consists of nodes that run the Kubernetes software, such as etcd and the Kubernetes API server. It runs in an account managed by AWS, and the Kubernetes API is exposed via the Amazon EKS endpoint associated with your cluster. Each Amazon EKS cluster control plane is single-tenant and unique, running on its own set of Amazon EC2 instances. - - * **Nodes** : Amazon EKS nodes are registered with the control plane and run in your AWS account. They connect to your cluster’s control plane via the API server endpoint and a certificate file created for your cluster. - - - - -To learn more about how the different components of Amazon EKS work, see [Configure networking for Amazon EKS clusters](./eks-networking.html). For connected clusters, see [Connect a Kubernetes cluster to an Amazon EKS Management Console with Amazon EKS Connector](./eks-connector.html). - -## Control plane architecture - -All data stored by the etcd nodes and associated Amazon EBS volumes is encrypted using AWS KMS. The control plane is provisioned across multiple Availability Zones and fronted by an Elastic Load Balancing Network Load Balancer. Amazon EKS also provisions elastic network interfaces in your VPC subnets to provide connectivity from the control plane instances to the nodes (for example, to support `kubectl exec`, logs, and proxy data flows). - -It’s important to note that in the Amazon EKS environment, `etcd` storage is limited to 8 GiB per [etcd upstream](https://etcd.io/docs/v3.5/dev-guide/limit/#storage-size-limit) guidance. You can optionally monitor a metric for the current database size by running the following command. - -###### Note - -If your cluster has a Kubernetes version below `1.28`, be sure to replace `apiserver_storage_size_bytes` with `apiserver_storage_db_total_size_in_bytes`. - +###### Topics @@ -39 +15 @@ If your cluster has a Kubernetes version below `1.28`, be sure to replace `apise - kubectl get --raw=/metrics | grep "apiserver_storage_size_bytes" + * [Understand the Kubernetes version lifecycle on EKS](./kubernetes-versions.html) @@ -41 +17 @@ If your cluster has a Kubernetes version below `1.28`, be sure to replace `apise -###### Topics + * [View Amazon EKS platform versions for each Kubernetes version](./platform-versions.html)