AWS eks documentation change
Summary
Changed documentation links from 'Configure a CNI for hybrid nodes' to 'Configure CNI for hybrid nodes' (removed article 'a' in link text)
Security assessment
The change is purely grammatical/stylistic, modifying article usage in documentation links. No security-related content was added, removed, or modified. The update affects only link text formatting, not any security configurations, authentication mechanisms, or vulnerability-related information.
Diff
diff --git a/eks/latest/userguide/hybrid-nodes-bottlerocket.md b/eks/latest/userguide/hybrid-nodes-bottlerocket.md index d33921c05..573d509c7 100644 --- a//eks/latest/userguide/hybrid-nodes-bottlerocket.md +++ b//eks/latest/userguide/hybrid-nodes-bottlerocket.md @@ -15 +15 @@ This topic describes how to connect hybrid nodes running Bottlerocket to an Amaz -Only VMware variants of Bottlerocket version v1.37.0 and above are supported with EKS Hybrid Nodes. VMware variants of Bottlerocket are available for Kubernetes versions v1.28 and above. The OS images for these variants include the kubelet, containerd, aws-iam-authenticator and other software prerequisites for EKS Hybrid Nodes. You can configure these components using a Bottlerocket [settings](https://github.com/bottlerocket-os/bottlerocket?tab=readme-ov-file#settings) file that includes base64 encoded user-data for the Bottlerocket bootstrap and admin containers. Configuring these settings enables Bottlerocket to use your hybrid nodes credentials provider to authenticate hybrid nodes to your cluster. After your hybrid nodes join the cluster, they will appear with status `Not Ready` in the Amazon EKS console and in Kubernetes-compatible tooling such as `kubectl`. After completing the steps on this page, proceed to [Configure a CNI for hybrid nodes](./hybrid-nodes-cni.html) to make your hybrid nodes ready to run applications. +Only VMware variants of Bottlerocket version v1.37.0 and above are supported with EKS Hybrid Nodes. VMware variants of Bottlerocket are available for Kubernetes versions v1.28 and above. The OS images for these variants include the kubelet, containerd, aws-iam-authenticator and other software prerequisites for EKS Hybrid Nodes. You can configure these components using a Bottlerocket [settings](https://github.com/bottlerocket-os/bottlerocket?tab=readme-ov-file#settings) file that includes base64 encoded user-data for the Bottlerocket bootstrap and admin containers. Configuring these settings enables Bottlerocket to use your hybrid nodes credentials provider to authenticate hybrid nodes to your cluster. After your hybrid nodes join the cluster, they will appear with status `Not Ready` in the Amazon EKS console and in Kubernetes-compatible tooling such as `kubectl`. After completing the steps on this page, proceed to [Configure CNI for hybrid nodes](./hybrid-nodes-cni.html) to make your hybrid nodes ready to run applications. @@ -233 +233 @@ Your nodes will have status `Not Ready`, which is expected and is due to the lac -To make your hybrid nodes ready to run applications, continue with the steps on [Configure a CNI for hybrid nodes](./hybrid-nodes-cni.html). +To make your hybrid nodes ready to run applications, continue with the steps on [Configure CNI for hybrid nodes](./hybrid-nodes-cni.html).