From e9c8d8bc3e42c88a56779293f22b5a5c69fdca3c Mon Sep 17 00:00:00 2001
From: Xiaopeng Han <hanxiaop8@outlook.com>
Date: Mon, 25 Sep 2023 15:33:35 +0800
Subject: [PATCH] fix test lint (#13925)

---
 .../config/analysis/ist0104/index.md          | 43 -------------------
 1 file changed, 43 deletions(-)
 delete mode 100644 content/en/docs/reference/config/analysis/ist0104/index.md

diff --git a/content/en/docs/reference/config/analysis/ist0104/index.md b/content/en/docs/reference/config/analysis/ist0104/index.md
deleted file mode 100644
index 0be5591e58..0000000000
--- a/content/en/docs/reference/config/analysis/ist0104/index.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: GatewayPortNotOnWorkload
-layout: analysis-message
-owner: istio/wg-user-experience-maintainers
-test: no
----
-
-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 port
-
-apiVersion: networking.istio.io/v1alpha3
-kind: Gateway
-metadata:
-  name: httpbin-gateway
-spec:
-  selector:
-    istio: ingressgateway
-  servers:
-  - port:
-      number: 80
-      name: http
-      protocol: HTTP
-    hosts:
-    - "*"
-  - port:
-      number: 8004
-      name: http2
-      protocol: HTTP
-    hosts:
-    - "*"
-{{< /text >}}
-
-In this example, the `GatewayPortNotOnWorkload` message occurs because this
-configuration uses port 8004, but a default `IngressGateway` is only open on ports
-80, 443, 31400, and 15443.
-
-To resolve this problem, change your gateway configuration to use a valid port
-on the workload and try again.