Update ingress-v1.md

While reading through the documentation, I noticed weird asterisk characters that seemed like they should be bullet points.  I kept reading and saw the formatting for `loadBalancer.ingress.ports.protocol`.  I liked how it organized the values into an easy to read list.

This proposed change formats the possible values for `rules.http.paths.pathType` to be a bullet point list, in (imo) a format that is easier to read.
This commit is contained in:
TheSamDickey
2022-04-06 23:33:52 -05:00
committed by GitHub
parent f481a2b3ca
commit 1be2b6e05c
@@ -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.