AWS eks documentation change
Summary
Updated legacy Cloud Provider documentation links to reference latest version instead of v2.7
Security assessment
The change only updates version numbers in URLs to point to latest documentation. No security-related content modifications or additions are present in the diff.
Diff
diff --git a/eks/latest/userguide/cluster-iam-role.md b/eks/latest/userguide/cluster-iam-role.md index 744896062..c3d373365 100644 --- a//eks/latest/userguide/cluster-iam-role.md +++ b//eks/latest/userguide/cluster-iam-role.md @@ -13 +13 @@ To contribute to this user guide, choose the **Edit this page on GitHub** link t -An Amazon EKS cluster IAM role is required for each cluster. Kubernetes clusters managed by Amazon EKS use this role to manage nodes and the [legacy Cloud Provider](https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.7/guide/service/annotations/#legacy-cloud-provider) uses this role to create load balancers with Elastic Load Balancing for services. +An Amazon EKS cluster IAM role is required for each cluster. Kubernetes clusters managed by Amazon EKS use this role to manage nodes and the [legacy Cloud Provider](https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/service/annotations/#legacy-cloud-provider) uses this role to create load balancers with Elastic Load Balancing for services. @@ -19 +19 @@ Before you can create Amazon EKS clusters, you must create an IAM role with eith - * A custom IAM policy. The minimal permissions that follow allows the Kubernetes cluster to manage nodes, but doesn’t allow the [legacy Cloud Provider](https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.7/guide/service/annotations/#legacy-cloud-provider) to create load balancers with Elastic Load Balancing. Your custom IAM policy must have at least the following permissions: + * A custom IAM policy. The minimal permissions that follow allows the Kubernetes cluster to manage nodes, but doesn’t allow the [legacy Cloud Provider](https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/service/annotations/#legacy-cloud-provider) to create load balancers with Elastic Load Balancing. Your custom IAM policy must have at least the following permissions: