Add IST0162 message description (#13800)

* Add IST0162 message description

* optimize

* optmize message
This commit is contained in:
Nicole LiHui 2023-10-09 09:13:21 +08:00 committed by GitHub
parent a02e6362ea
commit eeec04d8ab
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 94 additions and 0 deletions

View File

@ -0,0 +1,94 @@
---
title: GatewayPortNotDefinedOnService
layout: analysis-message
owner: istio/wg-user-experience-maintainers
test: n/a
---
This message occurs when a gateway (usually `istio-ingressgateway`) offers a
port that the Kubernetes service workload selected by the gateway does not.
For example, your Istio configuration contains these values:
{{< text yaml >}}
# Gateway with bogus ports
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: istio-ingressgateway
spec:
selector:
istio: ingressgateway
servers:
- port:
number: 80
name: http
protocol: HTTP
hosts:
- "*"
- port:
number: 8004
name: http2
protocol: HTTP
hosts:
- "*"
---
# Default Gateway Service
apiVersion: v1
kind: Service
metadata:
name: istio-ingressgateway
spec:
selector:
istio: ingressgateway
ports:
- name: status-port
port: 15021
protocol: TCP
targetPort: 15021
- name: http2
port: 80
protocol: TCP
targetPort: 8080
- name: https
port: 443
protocol: TCP
targetPort: 8443
{{< /text >}}
In this example, the `GatewayPortNotDefinedOnService` message occurs because this
configuration uses port 8004, but a default `IngressGateway` (named `istio-ingressgateway`) is only open on target ports
15021, 8080 and 8443.
To resolve this problem, change your gateway configuration to use a valid port
on the workload and try again.
Here's a corrected example:
{{< text yaml >}}
# Gateway with correct ports
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: istio-ingressgateway
spec:
selector:
istio: ingressgateway
servers:
- port:
number: 8080
name: http2
protocol: HTTP
hosts:
- "*"
- port:
number: 8443
name: https
protocol: HTTP
hosts:
- "*"
{{< /text >}}