AWS eks documentation change
Summary
Replaced markdown links with plain URLs and standardized region references using XML-style <shared> tags. Updated containerd documentation link formatting.
Security assessment
Changes involve documentation formatting and link presentation. No security-related content was added or modified. The updates focus on consistency in references to AWS regions and external resources, without addressing security features or vulnerabilities.
Diff
diff --git a/eks/latest/userguide/hybrid-nodes-nodeadm.md b/eks/latest/userguide/hybrid-nodes-nodeadm.md index 3a79bc4c8..2b1cd205f 100644 --- a//eks/latest/userguide/hybrid-nodes-nodeadm.md +++ b//eks/latest/userguide/hybrid-nodes-nodeadm.md @@ -17 +17 @@ The `nodeadm` version for hybrid nodes differs from the `nodeadm` version used f -The source code for the hybrid nodes `nodeadm` is published in the [https://github.com/aws/eks-hybrid](https://github.com/aws/eks-hybrid) GitHub repository. +The source code for the hybrid nodes `nodeadm` is published in the https://github.com/aws/eks-hybrid GitHub repository. @@ -267 +267 @@ The following is a sample `nodeConfig.yaml` when using AWS SSM hybrid activation - region: # AWS Region where the EKS cluster resides + region: # <shared id="AWS"/> Region where the EKS cluster resides @@ -285 +285 @@ When using AWS IAM Roles Anywhere as your on-premises credentials provider, the - region: # AWS Region where the EKS cluster resides + region: # <shared id="AWS"/> Region where the EKS cluster resides @@ -305 +305 @@ You can pass kubelet configuration and flags in your `nodeadm` configuration. Se - region: # AWS Region where the EKS cluster resides + region: # <shared id="AWS"/> Region where the EKS cluster resides @@ -326 +326 @@ You can pass custom containerd configuration in your `nodeadm` configuration. Th - region: # AWS Region where the EKS cluster resides + region: # <shared id="AWS"/> Region where the EKS cluster resides @@ -338 +338 @@ You can pass custom containerd configuration in your `nodeadm` configuration. Th -Containerd versions 1.x and 2.x use different configuration formats. Containerd 1.x uses config version 2, while containerd 2.x uses config version 3. Although containerd 2.x remains backward compatible with config version 2, config version 3 is recommended for optimal performance. Check your containerd version with `containerd --version` or review `nodeadm` install logs. For more details on config versioning, see [https://containerd.io/releases/](https://containerd.io/releases/) +Containerd versions 1.x and 2.x use different configuration formats. Containerd 1.x uses config version 2, while containerd 2.x uses config version 3. Although containerd 2.x remains backward compatible with config version 2, config version 3 is recommended for optimal performance. Check your containerd version with `containerd --version` or review `nodeadm` install logs. For more details on config versioning, see https://containerd.io/releases/ @@ -352 +352 @@ Red Hat Enterprise Linux (RHEL) 8 and RHEL 9 have SELinux enabled by default and - region: # AWS Region where the EKS cluster resides + region: # <shared id="AWS"/> Region where the EKS cluster resides