AWS eks documentation change
Summary
Multiple updates: 1) Added version compatibility details for containerd installations 2) Added new 'containerd-major-version-upgrade' skip option 3) Added note about containerd config version compatibility
Security assessment
Changes focus on installation compatibility and upgrade controls rather than security. The containerd version note addresses configuration formats but doesn't explicitly mention security vulnerabilities or protections. New skip option appears operational rather than security-focused.
Diff
diff --git a/eks/latest/userguide/hybrid-nodes-nodeadm.md b/eks/latest/userguide/hybrid-nodes-nodeadm.md index 8b2d12d51..3a79bc4c8 100644 --- a//eks/latest/userguide/hybrid-nodes-nodeadm.md +++ b//eks/latest/userguide/hybrid-nodes-nodeadm.md @@ -60 +60 @@ Name | Required | Description -`-s`, `--containerd-source` | FALSE | Source for `containerd`. `nodeadm` supports installing `containerd` from the OS distro, Docker packages, and skipping `containerd` install. **Values** `distro` \- This is the default value. `nodeadm` will install `containerd` package distributed by the node OS. `distro` is not a supported value for Red Hat Enterprise Linux (RHEL) operating systems. `docker` \- `nodeadm` will install `containerd` package built and distributed by Docker. `docker` is not a supported value for Amazon Linux 2023 `none` \- `nodeadm` will not install `containerd` package. You must manually install `containerd` before running `nodeadm init`. +`-s`, `--containerd-source` | FALSE | Source for `containerd`. `nodeadm` supports installing `containerd` from the OS distro, Docker packages, and skipping `containerd` install. **Values** `distro` \- This is the default value. `nodeadm` will install the latest `containerd` package distributed by the node OS that is compatible with the EKS Kubernetes version. `distro` is not a supported value for Red Hat Enterprise Linux (RHEL) operating systems. `docker` \- `nodeadm` will install the latest `containerd` package built and distributed by Docker that is compatible with the EKS Kubernetes version. `docker` is not a supported value for Amazon Linux 2023. `none` \- `nodeadm` will not install `containerd` package. You must manually install `containerd` before running `nodeadm init`. @@ -144 +144 @@ Name | Required | Description -`-s`, `--skip` | FALSE | Phases of upgrade to be skipped. It is not recommended to skip any of the phase unless it helps to fix an issue. **Values** `pod-validation` skips checking if all the no pods are running on the node, except daemon sets and static pods. `node-validation` skips checking if the node has been cordoned. `init-validation` skips checking if the node has been initialized successfully before running upgrade. +`-s`, `--skip` | FALSE | Phases of upgrade to be skipped. It is not recommended to skip any of the phase unless it helps to fix an issue. **Values** `pod-validation` skips checking if all the no pods are running on the node, except daemon sets and static pods. `node-validation` skips checking if the node has been cordoned. `init-validation` skips checking if the node has been initialized successfully before running upgrade. `containerd-major-version-upgrade` prevents containerd major version upgrades during node upgrade. @@ -335,0 +336,4 @@ You can pass custom containerd configuration in your `nodeadm` configuration. Th +###### Note + +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/) +