diff --git a/content/en/docs/tasks/traffic-management/ingress/gateway-api/index.md b/content/en/docs/tasks/traffic-management/ingress/gateway-api/index.md index 2d7e46d061..f506af2d5b 100644 --- a/content/en/docs/tasks/traffic-management/ingress/gateway-api/index.md +++ b/content/en/docs/tasks/traffic-management/ingress/gateway-api/index.md @@ -224,13 +224,12 @@ Note: only one address may be specified. #### Resource Attachment and Scaling -{{< warning >}} -Resource attachment is currently experimental. -{{< /warning >}} - Resources can be *attached* to a `Gateway` to customize it. However, most Kubernetes resources do not currently support attaching directly to a `Gateway`, but they can be attached to the corresponding generated `Deployment` and `Service` instead. -This is easily done because both of these resources are generated with name `-` and with a label `gateway.networking.k8s.io/gateway-name: `. +This is easily done because [the resources are generated with well-known labels](https://gateway-api.sigs.k8s.io/geps/gep-1762/#resource-attachment) (`gateway.networking.k8s.io/gateway-name: `) and names: + +* Gateway: `-` +* Waypoint: `` For example, to deploy a `Gateway` with a `HorizontalPodAutoscaler` and `PodDisruptionBudget`: