AWS eks documentation change
Summary
Fixed multiple typos including 'security pathces' to 'security patches', grammatical corrections, and removed duplicated 'support'
Security assessment
These are typographical corrections that improve clarity but don't change security meaning. The 'security patches' correction fixes a spelling error but doesn't indicate a new security vulnerability or feature. The warning about not terminating instances remains unchanged in substance.
Diff
diff --git a/eks/latest/userguide/eks-outposts-troubleshooting.md b/eks/latest/userguide/eks-outposts-troubleshooting.md index 0ceae3b96..81664a3bc 100644 --- a//eks/latest/userguide/eks-outposts-troubleshooting.md +++ b//eks/latest/userguide/eks-outposts-troubleshooting.md @@ -103 +103 @@ Amazon EKS automatically updates all existing local clusters to the latest platf -During an automatic platform-version rollout a cluster status changes to `UPDATING`. The update process consists of the replacement of all Kubernetes control-plane instances with new ones containing the latest security pathces and bugfixes released for the respective Kubernetes minor version. In general, a local cluster platform update process completes within less than 30 minutes and the cluster changes back to `ACTIVE` status. If a local cluster remains in the `UPDATING` state for an extended period of time, you may call `describe-cluster` to check for information about the cause in the `cluster.health` output field. +During an automatic platform-version rollout a cluster status changes to `UPDATING`. The update process consists of the replacement of all Kubernetes control-plane instances with new ones containing the latest security patches and bugfixes released for the respective Kubernetes minor version. In general, a local cluster platform update process completes within less than 30 minutes and the cluster changes back to `ACTIVE` status. If a local cluster remains in the `UPDATING` state for an extended period of time, you may call `describe-cluster` to check for information about the cause in the `cluster.health` output field. @@ -109 +109 @@ It is important to troubleshoot a local cluster stuck in `UPDATING` status and a -Do not terminate any managed EKS local cluster `Kubernetes` instances on Outposts unless explicitly instructed by AWS Support. This is specially important for local clusters stuck in `UPDATING` state because there’s a high probability that another control-plane nodes is not completely healthy and terminating the wrong instance could cause service interruption and risk local-cluster data loss. +Do not terminate any managed EKS local cluster `Kubernetes` instances on Outposts unless explicitly instructed by AWS Support. This is especially important for local clusters stuck in `UPDATING` state because there’s a high probability that another control-plane nodes is not completely healthy and terminating the wrong instance could cause service interruption and risk local-cluster data loss. @@ -141 +141 @@ The most common issues are the following: -When an Outpost gets disconnected from the AWS Region that it’s associated with, the Kubernetes cluster likely will continue working normally. However, if the cluster doesn’t work properly, follow the troubleshooting steps in [Prepare local Amazon EKS clusters on AWS Outposts for network disconnects](./eks-outposts-network-disconnects.html). If you encounter other issues, contact AWS Support. AWS Support can guide you on downloading and running a log collection tool. That way, you can collect logs from your Kubernetes cluster control plane instances and send them to AWS Support support for further investigation. +When an Outpost gets disconnected from the AWS Region that it’s associated with, the Kubernetes cluster likely will continue working normally. However, if the cluster doesn’t work properly, follow the troubleshooting steps in [Prepare local Amazon EKS clusters on AWS Outposts for network disconnects](./eks-outposts-network-disconnects.html). If you encounter other issues, contact AWS Support. AWS Support can guide you on downloading and running a log collection tool. That way, you can collect logs from your Kubernetes cluster control plane instances and send them to AWS Support for further investigation.