AWS eks documentation change
Summary
Added documentation for installing add-ons into custom Kubernetes namespaces.
Security assessment
The change introduces support for custom namespaces, which can improve resource isolation. However, this is presented as a general feature enhancement rather than a direct security measure. There is no evidence of addressing a security vulnerability.
Diff
diff --git a/eks/latest/userguide/creating-an-add-on.md b/eks/latest/userguide/creating-an-add-on.md index e84dcd9bf..78433c291 100644 --- a//eks/latest/userguide/creating-an-add-on.md +++ b//eks/latest/userguide/creating-an-add-on.md @@ -156 +156,3 @@ NOTE: Retaining the default role name enables EKS to pre-select the role for add - 6. Choose **Next**. + 6. If you want to install the add-on into a specific namespace, enter it in the **Namespace** field. For AWS and community add-ons, you can define a custom Kubernetes namespace to install the add-on into. For more information, see [Custom namespace for add-ons](./eks-add-ons.html#custom-namespace). + + 7. Choose **Next**. @@ -268,0 +271,2 @@ Here is an example of valid configuration values, in YAML format, that works wit + * If you want to install the add-on into a custom Kubernetes namespace, add the `--namespace-config 'namespace=<my-namespace>` option. This option is only available for AWS and community add-ons. For more information, see [Custom namespace for add-ons](./eks-add-ons.html#custom-namespace) +