AWS eks documentation change
Summary
Fixed grammatical errors (calculates->calculate) and clarified a sentence about using IAM roles with self-managed node groups.
Security assessment
The changes are grammatical corrections and minor clarifications about IAM role usage. There is no evidence of addressing a security vulnerability or weakness. The clarification about IAM roles is a best practice but not a security fix.
Diff
diff --git a/eks/latest/userguide/create-managed-node-group.md b/eks/latest/userguide/create-managed-node-group.md index cb2133c8e..4b9573726 100644 --- a//eks/latest/userguide/create-managed-node-group.md +++ b//eks/latest/userguide/create-managed-node-group.md @@ -118 +118 @@ Your instances can optionally assign a significantly higher number of IP address -Managed node groups calculates and applies a single value for the maximum number of Pods that can run on each node of your node group, based on instance type. If you create a node group with different instance types, the smallest value calculated across all instance types is applied as the maximum number of Pods that can run on every instance type in the node group. For more information about how this value is calculated, see [How maxPods is determined](./choosing-instance-type.html#max-pods-precedence). +Managed node groups calculate and apply a single value for the maximum number of Pods that can run on each node of your node group, based on instance type. If you create a node group with different instance types, the smallest value calculated across all instance types is applied as the maximum number of Pods that can run on every instance type in the node group. For more information about how this value is calculated, see [How maxPods is determined](./choosing-instance-type.html#max-pods-precedence). @@ -152 +152 @@ For a complete list of `eksctl` config file settings, see [Config file schema](h -If you didn’t specify an AMI ID in your launch template, managed node groups calculates and applies a single value for the maximum number of Pods that can run on each node of your node group, based on instance type. If you create a node group with different instance types, the smallest value calculated across all instance types is applied as the maximum number of Pods that can run on every instance type in the node group. For more information about how this value is calculated, see [How maxPods is determined](./choosing-instance-type.html#max-pods-precedence). +If you didn’t specify an AMI ID in your launch template, managed node groups calculate and apply a single value for the maximum number of Pods that can run on each node of your node group, based on instance type. If you create a node group with different instance types, the smallest value calculated across all instance types is applied as the maximum number of Pods that can run on every instance type in the node group. For more information about how this value is calculated, see [How maxPods is determined](./choosing-instance-type.html#max-pods-precedence). @@ -187 +187 @@ If you specified an AMI ID in your launch template, specify the maximum number o - * We recommend using a role that’s not currently in use by any self-managed node group. Otherwise, you plan to use with a new self-managed node group. For more information, see [Delete a managed node group from your cluster](./delete-managed-node-group.html). + * We recommend using a role that’s not currently in use by any self-managed node group, unless you plan to use it with a new self-managed node group. For more information, see [Delete a managed node group from your cluster](./delete-managed-node-group.html).