From edaecde0293dd0b5ddbe0c07630596af83150a4c Mon Sep 17 00:00:00 2001 From: Andrey Lebedev Date: Wed, 14 Feb 2024 15:53:58 +0100 Subject: [PATCH] docs: ingress subnets annotation - clarify locale differences --- docs/guide/ingress/annotations.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/guide/ingress/annotations.md b/docs/guide/ingress/annotations.md index ff8a893f0..6f2f421c6 100644 --- a/docs/guide/ingress/annotations.md +++ b/docs/guide/ingress/annotations.md @@ -226,7 +226,10 @@ Traffic Routing can be controlled with following annotations: - `alb.ingress.kubernetes.io/subnets` specifies the [Availability Zone](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html)s that the ALB will route traffic to. See [Load Balancer subnets](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-subnets.html) for more details. !!!note "" - You must specify at least two subnets in different AZs. Either subnetID or subnetName(Name tag on subnets) can be used. + You must specify at least two subnets in different AZs unless utilizing the outpost locale, in which case a single subnet suffices. Either subnetID or subnetName(Name tag on subnets) can be used. + + !!!note "" + You must not mix subnets from different locales: availability-zone, local-zone, wavelength-zone, outpost. !!!tip You can enable subnet auto discovery to avoid specifying this annotation on every Ingress. See [Subnet Discovery](../../deploy/subnet_discovery.md) for instructions.