public static interface V1Networking.HTTPIngressPathOrBuilder
extends com.google.protobuf.MessageOrBuilder
| Modifier and Type | Method and Description |
|---|---|
V1Networking.IngressBackend |
getBackend()
Backend defines the referenced service endpoint to which the traffic
will be forwarded to.
|
V1Networking.IngressBackendOrBuilder |
getBackendOrBuilder()
Backend defines the referenced service endpoint to which the traffic
will be forwarded to.
|
String |
getPath()
Path is matched against the path of an incoming request.
|
com.google.protobuf.ByteString |
getPathBytes()
Path is matched against the path of an incoming request.
|
String |
getPathType()
PathType determines the interpretation of the Path matching.
|
com.google.protobuf.ByteString |
getPathTypeBytes()
PathType determines the interpretation of the Path matching.
|
boolean |
hasBackend()
Backend defines the referenced service endpoint to which the traffic
will be forwarded to.
|
boolean |
hasPath()
Path is matched against the path of an incoming request.
|
boolean |
hasPathType()
PathType determines the interpretation of the Path matching.
|
findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneofboolean hasPath()
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 '/' and must be present when using PathType with value "Exact" or "Prefix". +optional
optional string path = 1;String getPath()
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 '/' and must be present when using PathType with value "Exact" or "Prefix". +optional
optional string path = 1;com.google.protobuf.ByteString getPathBytes()
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 '/' and must be present when using PathType with value "Exact" or "Prefix". +optional
optional string path = 1;boolean hasPathType()
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 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.
optional string pathType = 3;String getPathType()
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 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.
optional string pathType = 3;com.google.protobuf.ByteString getPathTypeBytes()
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 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.
optional string pathType = 3;boolean hasBackend()
Backend defines the referenced service endpoint to which the traffic will be forwarded to.
optional .k8s.io.api.networking.v1.IngressBackend backend = 2;V1Networking.IngressBackend getBackend()
Backend defines the referenced service endpoint to which the traffic will be forwarded to.
optional .k8s.io.api.networking.v1.IngressBackend backend = 2;V1Networking.IngressBackendOrBuilder getBackendOrBuilder()
Backend defines the referenced service endpoint to which the traffic will be forwarded to.
optional .k8s.io.api.networking.v1.IngressBackend backend = 2;Copyright © 2023. All rights reserved.