From 0e4d4b686133f12f8760a9eed38076f8fd71d648 Mon Sep 17 00:00:00 2001 From: Nate W <4453979+nate-double-u@users.noreply.github.com> Date: Wed, 27 Apr 2022 16:13:55 +0000 Subject: [PATCH] Update API Reference multi-pages for v1.24 --- .../kubernetes-api/service-resources/ingress-v1.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/content/en/docs/reference/kubernetes-api/service-resources/ingress-v1.md b/content/en/docs/reference/kubernetes-api/service-resources/ingress-v1.md index 4ce6c8708b..5a8bb7fd8e 100644 --- a/content/en/docs/reference/kubernetes-api/service-resources/ingress-v1.md +++ b/content/en/docs/reference/kubernetes-api/service-resources/ingress-v1.md @@ -109,16 +109,14 @@ IngressSpec describes the Ingress the user wishes to exist. - **rules.http.paths.pathType** (string), required - PathType determines the interpretation of the Path matching. PathType can be one of the following enum values: - - `"Exact"` Matches the URL path exactly. - - `"Prefix"` Matches based on a URL path prefix split by '/'. Matching is + PathType determines the interpretation of the Path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching is done on a path element by element basis. A path element refers is the list of labels in the path split by the '/' separator. A request is a match for path p if every p is an element-wise prefix of p of the request path. Note that if the last element of the path is a substring of the last element in request path, it is not a match (e.g. /foo/bar matches /foo/bar/baz, but does not match /foo/barbaz). - - `"ImplementationSpecific"` Interpretation of the Path matching is up to + * ImplementationSpecific: Interpretation of the Path matching is up to the IngressClass. Implementations can treat this as a separate PathType or treat it identically to Prefix or Exact path types. Implementations are required to support all path types.