AWS eks documentation change
Summary
Updated AWS Load Balancer Controller documentation links from version-specific (v2.7) to 'latest' path
Security assessment
The changes update documentation URLs but maintain the same security-related recommendations (disabling shield/WAF flags). No new security context or vulnerability fixes are introduced in these link updates.
Diff
diff --git a/eks/latest/userguide/private-clusters.md b/eks/latest/userguide/private-clusters.md index 2e6d86744..5abdbc051 100644 --- a//eks/latest/userguide/private-clusters.md +++ b//eks/latest/userguide/private-clusters.md @@ -97 +97 @@ Amazon EKS | com.amazonaws.`region-code`.eks - * You can use the [AWS Load Balancer Controller](./aws-load-balancer-controller.html) to deploy AWS Application Load Balancers (ALB) and Network Load Balancers to your private cluster. When deploying it, you should use [command line flags](https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.7/deploy/configurations/#controller-command-line-flags) to set `enable-shield`, `enable-waf`, and `enable-wafv2` to false. [Certificate discovery](https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.7/guide/ingress/cert_discovery/#discover-via-ingress-rule-host) with hostnames from Ingress objects isn’t supported. This is because the controller needs to reach AWS Certificate Manager, which doesn’t have a VPC interface endpoint. + * You can use the [AWS Load Balancer Controller](./aws-load-balancer-controller.html) to deploy AWS Application Load Balancers (ALB) and Network Load Balancers to your private cluster. When deploying it, you should use [command line flags](https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/deploy/configurations/#controller-command-line-flags) to set `enable-shield`, `enable-waf`, and `enable-wafv2` to false. [Certificate discovery](https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/ingress/cert_discovery/#discover-via-ingress-rule-host) with hostnames from Ingress objects isn’t supported. This is because the controller needs to reach AWS Certificate Manager, which doesn’t have a VPC interface endpoint.