Auto-generated derived type for HTTPRouteSpec via CustomResource
ParentReference identifies an API object (usually a Gateway) that can be considered
a parent of this resource (usually a route). There are two kinds of parent resources
with “Core” support:
HTTPRouteRule defines semantics for matching an HTTP request based on
conditions (matches), processing it (filters), and forwarding the request to
an API object (backendRefs).
HTTPBackendRef defines how a HTTPRoute forwards a HTTP request.
HTTPRouteFilter defines processing steps that must be completed during the
request or response lifecycle. HTTPRouteFilters are meant as an extension
point to express processing that may be done in Gateway implementations. Some
examples include request or response modification, implementing
authentication strategies, rate-limiting, and traffic shaping. API
guarantee/conformance is defined based on the type of the filter.
ExtensionRef is an optional, implementation-specific extension to the
“filter” behavior. For example, resource “myroutefilter” in group
“networking.example.net”). ExtensionRef MUST NOT be used for core and
extended filters.
RequestHeaderModifier defines a schema for a filter that modifies request
headers.
HTTPHeader represents an HTTP Header name and value as defined by RFC 7230.
HTTPHeader represents an HTTP Header name and value as defined by RFC 7230.
RequestMirror defines a schema for a filter that mirrors requests.
Requests are sent to the specified destination, but responses from
that destination are ignored.
BackendRef references a resource where mirrored requests are sent.
Fraction represents the fraction of requests that should be
mirrored to BackendRef.
RequestRedirect defines a schema for a filter that responds to the
request with an HTTP redirection.
Path defines parameters used to modify the path of the incoming request.
The modified path is then used to construct the Location header. When
empty, the request path is used as-is.
ResponseHeaderModifier defines a schema for a filter that modifies response
headers.
HTTPHeader represents an HTTP Header name and value as defined by RFC 7230.
HTTPHeader represents an HTTP Header name and value as defined by RFC 7230.
URLRewrite defines a schema for a filter that modifies a request during forwarding.
Path defines a path rewrite.
HTTPRouteFilter defines processing steps that must be completed during the
request or response lifecycle. HTTPRouteFilters are meant as an extension
point to express processing that may be done in Gateway implementations. Some
examples include request or response modification, implementing
authentication strategies, rate-limiting, and traffic shaping. API
guarantee/conformance is defined based on the type of the filter.
ExtensionRef is an optional, implementation-specific extension to the
“filter” behavior. For example, resource “myroutefilter” in group
“networking.example.net”). ExtensionRef MUST NOT be used for core and
extended filters.
RequestHeaderModifier defines a schema for a filter that modifies request
headers.
HTTPHeader represents an HTTP Header name and value as defined by RFC 7230.
HTTPHeader represents an HTTP Header name and value as defined by RFC 7230.
RequestMirror defines a schema for a filter that mirrors requests.
Requests are sent to the specified destination, but responses from
that destination are ignored.
BackendRef references a resource where mirrored requests are sent.
Fraction represents the fraction of requests that should be
mirrored to BackendRef.
RequestRedirect defines a schema for a filter that responds to the
request with an HTTP redirection.
Path defines parameters used to modify the path of the incoming request.
The modified path is then used to construct the Location header. When
empty, the request path is used as-is.
ResponseHeaderModifier defines a schema for a filter that modifies response
headers.
HTTPHeader represents an HTTP Header name and value as defined by RFC 7230.
HTTPHeader represents an HTTP Header name and value as defined by RFC 7230.
URLRewrite defines a schema for a filter that modifies a request during forwarding.
Path defines a path rewrite.
HTTPRouteMatch defines the predicate used to match requests to a given
action. Multiple match types are ANDed together, i.e. the match will
evaluate to true only if all conditions are satisfied.
HTTPHeaderMatch describes how to select a HTTP route by matching HTTP request
headers.
Path specifies a HTTP request path matcher. If this field is not
specified, a default prefix match on the “/” path is provided.
HTTPQueryParamMatch describes how to select a HTTP route by matching HTTP
query parameters.
Retry defines the configuration for when to retry an HTTP request.
SessionPersistence defines and configures session persistence
for the route rule.
CookieConfig provides configuration settings that are specific
to cookie-based session persistence.
Timeouts defines the timeouts that can be configured for an HTTP request.
Spec defines the desired state of HTTPRoute.
Status defines the current state of HTTPRoute.
RouteParentStatus describes the status of a route with respect to an
associated Parent.
ParentRef corresponds with a ParentRef in the spec that this
RouteParentStatus struct describes the status of.
Path defines parameters used to modify the path of the incoming request.
The modified path is then used to construct the Location header. When
empty, the request path is used as-is.
RequestRedirect defines a schema for a filter that responds to the
request with an HTTP redirection.
RequestRedirect defines a schema for a filter that responds to the
request with an HTTP redirection.
HTTPRouteFilter defines processing steps that must be completed during the
request or response lifecycle. HTTPRouteFilters are meant as an extension
point to express processing that may be done in Gateway implementations. Some
examples include request or response modification, implementing
authentication strategies, rate-limiting, and traffic shaping. API
guarantee/conformance is defined based on the type of the filter.
Path defines a path rewrite.
Path defines parameters used to modify the path of the incoming request.
The modified path is then used to construct the Location header. When
empty, the request path is used as-is.
RequestRedirect defines a schema for a filter that responds to the
request with an HTTP redirection.
RequestRedirect defines a schema for a filter that responds to the
request with an HTTP redirection.
HTTPRouteFilter defines processing steps that must be completed during the
request or response lifecycle. HTTPRouteFilters are meant as an extension
point to express processing that may be done in Gateway implementations. Some
examples include request or response modification, implementing
authentication strategies, rate-limiting, and traffic shaping. API
guarantee/conformance is defined based on the type of the filter.
Path defines a path rewrite.
HTTPHeaderMatch describes how to select a HTTP route by matching HTTP request
headers.
HTTPRouteMatch defines the predicate used to match requests to a given
action. Multiple match types are ANDed together, i.e. the match will
evaluate to true only if all conditions are satisfied.
Path specifies a HTTP request path matcher. If this field is not
specified, a default prefix match on the “/” path is provided.
HTTPQueryParamMatch describes how to select a HTTP route by matching HTTP
query parameters.
CookieConfig provides configuration settings that are specific
to cookie-based session persistence.
SessionPersistence defines and configures session persistence
for the route rule.