AWS eks documentation change
Summary
Minor grammatical corrections, typo fixes, and capitalization updates throughout the Kubernetes concepts documentation
Security assessment
The changes are purely editorial: fixing grammar (e.g., 'tend' to 'tends'), typos ('computer' to 'compute'), and capitalization ('IOT' to 'IoT', 'VMWare' to 'VMware'). No security-related content was added, modified, or referenced in the changes.
Diff
diff --git a/eks/latest/userguide/kubernetes-concepts.md b/eks/latest/userguide/kubernetes-concepts.md index 6ded982a2..907da57d3 100644 --- a//eks/latest/userguide/kubernetes-concepts.md +++ b//eks/latest/userguide/kubernetes-concepts.md @@ -71 +71 @@ To achieve its goals, Kubernetes has the following attributes: - * **Portable** — Many organizations have standardized their operations on Kubernetes because it allows them to manage all of their application needs in the same way. Developers can use the same pipelines to build and store containerized applications. Those applications can then be deployed to Kubernetes clusters running on-premises, in clouds, on point-of-sales terminals in restaurants, or on IOT devices dispersed across company’s remote sites. Its open source nature makes it possible for people to develop these special Kubernetes distributions, along will tools needed to manage them. + * **Portable** — Many organizations have standardized their operations on Kubernetes because it allows them to manage all of their application needs in the same way. Developers can use the same pipelines to build and store containerized applications. Those applications can then be deployed to Kubernetes clusters running on-premises, in clouds, on point-of-sales terminals in restaurants, or on IoT devices dispersed across a company’s remote sites. Its open source nature makes it possible for people to develop these special Kubernetes distributions, along with tools needed to manage them. @@ -80 +80 @@ Kubernetes source code is freely available, so with your own equipment you could - * **Hardware** — If you don’t have hardware available to run Kubernetes per your requirements, a cloud provider such as AWS Amazon EKS can save you on upfront costs. With Amazon EKS, this means that you can consume the best cloud resources offered by AWS, including computer instances (Amazon Elastic Compute Cloud), your own private environment (Amazon VPC), central identity and permissions management (IAM), and storage (Amazon EBS). AWS manages the computers, networks, data centers, and all the other physical components needed to run Kubernetes. Likewise, you don’t have to plan your datacenter to handle the maximum capacity on your highest-demand days. For Amazon EKS Anywhere, or other on premises Kubernetes clusters, you are responsible for managing the infrastructure used in your Kubernetes deployments, but you can still rely on AWS to help you keep Kubernetes up to date. + * **Hardware** — If you don’t have hardware available to run Kubernetes per your requirements, a cloud provider such as AWS Amazon EKS can save you on upfront costs. With Amazon EKS, this means that you can consume the best cloud resources offered by AWS, including compute instances (Amazon Elastic Compute Cloud), your own private environment (Amazon VPC), central identity and permissions management (IAM), and storage (Amazon EBS). AWS manages the computers, networks, data centers, and all the other physical components needed to run Kubernetes. Likewise, you don’t have to plan your datacenter to handle the maximum capacity on your highest-demand days. For Amazon EKS Anywhere, or other on premises Kubernetes clusters, you are responsible for managing the infrastructure used in your Kubernetes deployments, but you can still rely on AWS to help you keep Kubernetes up to date. @@ -111 +111 @@ If your job is to start and manage Kubernetes clusters, you should know how Kube -Tools for managing clusters handle the overlap between the Kubernetes services and the underlying hardware provider. For that reason, automation of these tasks tend to be done by the Kubernetes provider (such as Amazon EKS or Amazon EKS Anywhere) using tools that are specific to the provider. For example, to start an Amazon EKS cluster you can use `eksctl create cluster`, while for Amazon EKS Anywhere you can use `eksctl anywhere create cluster`. Note that while these commands create a Kubernetes cluster, they are specific to the provider and are not part of the Kubernetes project itself. +Tools for managing clusters handle the overlap between the Kubernetes services and the underlying hardware provider. For that reason, automation of these tasks tends to be done by the Kubernetes provider (such as Amazon EKS or Amazon EKS Anywhere) using tools that are specific to the provider. For example, to start an Amazon EKS cluster you can use `eksctl create cluster`, while for Amazon EKS Anywhere you can use `eksctl anywhere create cluster`. Note that while these commands create a Kubernetes cluster, they are specific to the provider and are not part of the Kubernetes project itself. @@ -130 +130 @@ In AWS Cloud, you can create [Amazon EKS](https://docs.aws.amazon.com/eks/) clus -To run your clusters on your own on-premises computers and networks, Amazon offers [Amazon EKS Anywhere](https://anywhere.eks.amazonaws.com/). Instead of the AWS Cloud being the provider, you have the choice of running Amazon EKS Anywhere on [VMWare vSphere](https://anywhere.eks.amazonaws.com/docs/getting-started/vsphere/), [bare metal](https://anywhere.eks.amazonaws.com/docs/getting-started/baremetal/) ([Tinkerbell provider](https://tinkerbell.org)), [Snow](https://anywhere.eks.amazonaws.com/docs/getting-started/snow/), [CloudStack](https://anywhere.eks.amazonaws.com/docs/getting-started/cloudstack/), or [Nutanix](https://anywhere.eks.amazonaws.com/docs/getting-started/nutanix/) platforms using your own equipment. +To run your clusters on your own on-premises computers and networks, Amazon offers [Amazon EKS Anywhere](https://anywhere.eks.amazonaws.com/). Instead of the AWS Cloud being the provider, you have the choice of running Amazon EKS Anywhere on [VMware vSphere](https://anywhere.eks.amazonaws.com/docs/getting-started/vsphere/), [bare metal](https://anywhere.eks.amazonaws.com/docs/getting-started/baremetal/) ([Tinkerbell provider](https://tinkerbell.org)), [Snow](https://anywhere.eks.amazonaws.com/docs/getting-started/snow/), [CloudStack](https://anywhere.eks.amazonaws.com/docs/getting-started/cloudstack/), or [Nutanix](https://anywhere.eks.amazonaws.com/docs/getting-started/nutanix/) platforms using your own equipment. @@ -140 +140 @@ Kubernetes cluster components are divided into two major areas: control plane an -The control plane consists of a set of services that manage the cluster. These services may all be running on a single computer or may be spread across multiple computers. Internally, these are referred to as Control Plane Instances (CPIs). How CPIs are run depends on the size of the cluster and requirements for high availability. As demand increase in the cluster, a control plane service can scale to provide more instances of that service, with requests being load balanced between the instances. +The control plane consists of a set of services that manage the cluster. These services may all be running on a single computer or may be spread across multiple computers. Internally, these are referred to as Control Plane Instances (CPIs). How CPIs are run depends on the size of the cluster and requirements for high availability. As demand increases in the cluster, a control plane service can scale to provide more instances of that service, with requests being load balanced between the instances. @@ -142 +142 @@ The control plane consists of a set of services that manage the cluster. These s -Tasks that components of the Kubernetes control plane performs include: +Tasks that components of the Kubernetes control plane perform include: @@ -165 +165 @@ When you first create a Kubernetes cluster, some cluster creation tools allow yo - * **Run containers on a node (container runtime)** — The [Container Runtime](https://kubernetes.io/docs/setup/production-environment/container-runtimes/) on each node manages the containers requested for each Pod assigned to the node. That means that it can pull container images from the appropriate registry, run the container, stop it, and responds to queries about the container. The default container runtime is [containerd](https://github.com/containerd/containerd/blob/main/docs/getting-started.md). As of Kubernetes 1.24, the special integration of Docker (`dockershim`) that could be used as the container runtime was dropped from Kubernetes. While you can still use Docker to test and run containers on your local system, to use Docker with Kubernetes you would now have to [Install Docker Engine](https://docs.docker.com/engine/install/#server) on each node to use it with Kubernetes. + * **Run containers on a node (container runtime)** — The [Container Runtime](https://kubernetes.io/docs/setup/production-environment/container-runtimes/) on each node manages the containers requested for each Pod assigned to the node. That means that it can pull container images from the appropriate registry, run the container, stop it, and respond to queries about the container. The default container runtime is [containerd](https://github.com/containerd/containerd/blob/main/docs/getting-started.md). As of Kubernetes 1.24, the special integration of Docker (`dockershim`) that could be used as the container runtime was dropped from Kubernetes. While you can still use Docker to test and run containers on your local system, to use Docker with Kubernetes you would now have to [Install Docker Engine](https://docs.docker.com/engine/install/#server) on each node to use it with Kubernetes. @@ -267 +267 @@ The method you would choose for deploying Pods depends on the type of applicatio -With applications often deployed as a set of microservices that moved around to different places, Kubernetes needed a way for those microservices to be able to find each other. Also, for others to access an application outside of the Kubernetes cluster, Kubernetes needed a way to expose that application on outside addresses and ports. These networking-related features are done with Service and Ingress objects, respectively: +With applications often deployed as a set of microservices that move around to different places, Kubernetes needed a way for those microservices to be able to find each other. Also, for others to access an application outside of the Kubernetes cluster, Kubernetes needed a way to expose that application on outside addresses and ports. These networking-related features are done with Service and Ingress objects, respectively: