istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

update resource attachment (#16030) 

* update resource attachment

* add link to GEP
This commit is contained in:
Craig Box 2024-12-04 05:33:28 +13:00 committed by GitHub
parent 18bca5cb1a
commit 77f0da212a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
content/en/docs/tasks/traffic-management/ingress/gateway-api/index.md
View File

@ -224,13 +224,12 @@ Note: only one address may be specified.
#### Resource Attachment and Scaling #### Resource Attachment and Scaling
{{< warning >}}
Resource attachment is currently experimental.
{{< /warning >}}
Resources can be *attached* to a `Gateway` to customize it. 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. 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 `<gateway name>-<gateway class name>` and with a label `gateway.networking.k8s.io/gateway-name: <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: <gateway name>`) and names:
* Gateway: `<gateway name>-<gateway class name>`
* Waypoint: `<gateway name>`
For example, to deploy a `Gateway` with a `HorizontalPodAutoscaler` and `PodDisruptionBudget`: For example, to deploy a `Gateway` with a `HorizontalPodAutoscaler` and `PodDisruptionBudget`: