forked from yannh/kubernetes-json-schema
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathhttpingresspath.json
28 lines (28 loc) · 1.85 KB
/
httpingresspath.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
{
"description": "HTTPIngressPath associates a path with a backend. Incoming urls matching the path are forwarded to the backend.",
"properties": {
"backend": {
"$ref": "_definitions.json#/definitions/io.k8s.api.networking.v1beta1.IngressBackend",
"description": "Backend defines the referenced service endpoint to which the traffic will be forwarded to."
},
"path": {
"description": "Path is matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional \"path\" part of a URL as defined by RFC 3986. Paths must begin with a '/'. When unspecified, all paths from incoming requests are matched.",
"type": [
"string",
"null"
]
},
"pathType": {
"description": "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\n done on a path element by element basis. A path element refers is the\n list of labels in the path split by the '/' separator. A request is a\n match for path p if every p is an element-wise prefix of p of the\n request path. Note that if the last element of the path is a substring\n of the last element in request path, it is not a match (e.g. /foo/bar\n matches /foo/bar/baz, but does not match /foo/barbaz).\n* ImplementationSpecific: Interpretation of the Path matching is up to\n the IngressClass. Implementations can treat this as a separate PathType\n or treat it identically to Prefix or Exact path types.\nImplementations are required to support all path types. Defaults to ImplementationSpecific.",
"type": [
"string",
"null"
]
}
},
"required": [
"backend"
],
"type": "object",
"$schema": "http://json-schema.org/schema#"
}