AWS eks documentation change
Summary
Minor text correction changing 'a CNI' to 'CNI' in uninstall documentation
Security assessment
This is a grammatical improvement without any security implications. The change does not alter security-related content or address any vulnerabilities.
Diff
diff --git a/eks/latest/userguide/hybrid-nodes-nodeadm.md b/eks/latest/userguide/hybrid-nodes-nodeadm.md index 6528ab420..8b2d12d51 100644 --- a//eks/latest/userguide/hybrid-nodes-nodeadm.md +++ b//eks/latest/userguide/hybrid-nodes-nodeadm.md @@ -157 +157 @@ Name | Required | Description -The `nodeadm uninstall` command stops and removes the artifacts `nodeadm` installs during `nodeadm install`, including the kubelet and containerd. Note, the uninstall command does not drain or delete your hybrid nodes from your cluster. You must run the drain and delete operations separately, see [Remove hybrid nodes](./hybrid-nodes-remove.html) for more information. By default, `nodeadm uninstall` will not proceed if there are pods remaining on the node. Similarly, `nodeadm uninstall` does not remove CNI dependencies or dependencies of other Kubernetes add-ons you run on your cluster. To fully remove the CNI installation from your host, see the instructions at [Configure a CNI for hybrid nodes](./hybrid-nodes-cni.html). If you are using AWS SSM hybrid activations as your on-premises credentials provider, the `nodeadm uninstall` command deregisters your hosts as AWS SSM managed instances. +The `nodeadm uninstall` command stops and removes the artifacts `nodeadm` installs during `nodeadm install`, including the kubelet and containerd. Note, the uninstall command does not drain or delete your hybrid nodes from your cluster. You must run the drain and delete operations separately, see [Remove hybrid nodes](./hybrid-nodes-remove.html) for more information. By default, `nodeadm uninstall` will not proceed if there are pods remaining on the node. Similarly, `nodeadm uninstall` does not remove CNI dependencies or dependencies of other Kubernetes add-ons you run on your cluster. To fully remove the CNI installation from your host, see the instructions at [Configure CNI for hybrid nodes](./hybrid-nodes-cni.html). If you are using AWS SSM hybrid activations as your on-premises credentials provider, the `nodeadm uninstall` command deregisters your hosts as AWS SSM managed instances.