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

gateway-api: fix gateway deployment name (#12601) 

* gateway-api: fix gateway deployment name

* regen
This commit is contained in:
Frank Budinsky 2023-02-07 17:23:42 -05:00 committed by GitHub
parent 8713ad1f41
commit 410dad76ed
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -231,7 +231,7 @@ Resource attachment is currently experimental.
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 the same name as the `Gateway` and with a label `istio.io/gateway-name: <gateway name>`.
This is easily done because both of these resources are generated with name `<gateway name>-<gateway class name>` and with a label `istio.io/gateway-name: <gateway name>`.
For example, to deploy a `Gateway` with a `HorizontalPodAutoscaler` and `PodDisruptionBudget`:
@ -261,7 +261,7 @@ spec:
scaleTargetRef:
apiVersion: apps/v1
kind: Deployment
name: gateway
name: gateway-istio
minReplicas: 2
maxReplicas: 5
metrics:

2
content/en/docs/tasks/traffic-management/ingress/gateway-api/snips.sh
View File

@ -180,7 +180,7 @@ spec:
scaleTargetRef:
apiVersion: apps/v1
kind: Deployment
name: gateway
name: gateway-istio
minReplicas: 2
maxReplicas: 5
metrics: