Struct gateway_api::experimental::grpcroutes::GRPCRouteSpec
source · pub struct GRPCRouteSpec {
pub hostnames: Option<Vec<String>>,
pub parent_refs: Option<Vec<GRPCRouteParentRefs>>,
pub rules: Option<Vec<GRPCRouteRules>>,
}
Expand description
Spec defines the desired state of GRPCRoute.
Fields
hostnames: Option<Vec<String>>
Hostnames defines a set of hostname to match against the GRPC Host header to select a GRPCRoute to process the request. This matches the RFC 1123 definition of a hostname with 2 notable exceptions:
- IPs are not allowed. 2. A hostname may be prefixed with a wildcard label (
*.
). The wildcard label MUST appear by itself as the first label. If a hostname is specified by both the Listener and GRPCRoute, there MUST be at least one intersecting hostname for the GRPCRoute to be attached to the Listener. For example:
- A Listener with
test.example.com
as the hostname matches GRPCRoutes that have either not specified any hostnames, or have specified at least one oftest.example.com
or*.example.com
. * A Listener with*.example.com
as the hostname matches GRPCRoutes that have either not specified any hostnames or have specified at least one hostname that matches the Listener hostname. For example,test.example.com
and*.example.com
would both match. On the other hand,example.com
andtest.example.net
would not match. Hostnames that are prefixed with a wildcard label (*.
) are interpreted as a suffix match. That means that a match for*.example.com
would match bothtest.example.com
, andfoo.test.example.com
, but notexample.com
. If both the Listener and GRPCRoute have specified hostnames, any GRPCRoute hostnames that do not match the Listener hostname MUST be ignored. For example, if a Listener specified*.example.com
, and the GRPCRoute specifiedtest.example.com
andtest.example.net
,test.example.net
MUST NOT be considered for a match. If both the Listener and GRPCRoute have specified hostnames, and none match with the criteria above, then the GRPCRoute is not accepted. The implementation MUST raise an ‘Accepted’ Condition with a status ofFalse
in the corresponding RouteParentStatus. If a Route (A) of type HTTPRoute or GRPCRoute is attached to a Listener and that listener already has another Route (B) of the other type attached and the intersection of the hostnames of A and B is non-empty, then the implementation MUST accept exactly one of these two routes, determined by the following criteria, in order: - The oldest Route based on creation timestamp. * The Route appearing first in alphabetical order by “{namespace}/{name}”. The rejected Route MUST raise an ‘Accepted’ condition with a status of ‘False’ in the corresponding RouteParentStatus. Support: Core
parent_refs: Option<Vec<GRPCRouteParentRefs>>
ParentRefs references the resources (usually Gateways) that a Route wants to be attached to. Note that the referenced parent resource needs to allow this for the attachment to be complete. For Gateways, that means the Gateway needs to allow attachment from Routes of this kind and namespace. The only kind of parent resource with “Core” support is Gateway. This API may be extended in the future to support additional kinds of parent resources such as one of the route kinds. It is invalid to reference an identical parent more than once. It is valid to reference multiple distinct sections within the same parent resource, such as 2 Listeners within a Gateway. It is possible to separately reference multiple distinct objects that may be collapsed by an implementation. For example, some implementations may choose to merge compatible Gateway Listeners together. If that is the case, the list of routes attached to those resources should also be merged.
rules: Option<Vec<GRPCRouteRules>>
Rules are a list of GRPC matchers, filters and actions.
Trait Implementations
sourceimpl Clone for GRPCRouteSpec
impl Clone for GRPCRouteSpec
sourcefn clone(&self) -> GRPCRouteSpec
fn clone(&self) -> GRPCRouteSpec
1.0.0 · sourcefn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moresourceimpl Debug for GRPCRouteSpec
impl Debug for GRPCRouteSpec
sourceimpl<'de> Deserialize<'de> for GRPCRouteSpec
impl<'de> Deserialize<'de> for GRPCRouteSpec
sourcefn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
__D: Deserializer<'de>,
fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
__D: Deserializer<'de>,
sourceimpl JsonSchema for GRPCRouteSpec
impl JsonSchema for GRPCRouteSpec
sourcefn schema_name() -> String
fn schema_name() -> String
sourcefn json_schema(gen: &mut SchemaGenerator) -> Schema
fn json_schema(gen: &mut SchemaGenerator) -> Schema
sourcefn is_referenceable() -> bool
fn is_referenceable() -> bool
$ref
keyword. Read more