Merge pull request #32793 from TheSamDickey/patch-1
Update ingress-v1 rules.http.paths.pathType values
This commit is contained in:
commit
74b148081f
|
|
@ -109,14 +109,16 @@ IngressSpec describes the Ingress the user wishes to exist.
|
||||||
|
|
||||||
- **rules.http.paths.pathType** (string), required
|
- **rules.http.paths.pathType** (string), required
|
||||||
|
|
||||||
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
|
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
|
||||||
done on a path element by element basis. A path element refers is the
|
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
|
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
|
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
|
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
|
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).
|
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
|
the IngressClass. Implementations can treat this as a separate PathType
|
||||||
or treat it identically to Prefix or Exact path types.
|
or treat it identically to Prefix or Exact path types.
|
||||||
Implementations are required to support all path types.
|
Implementations are required to support all path types.
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue