apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  annotations:
    api-approved.kubernetes.io: https://github.com/kubernetes-sigs/gateway-api/pull/2997
    gateway.networking.k8s.io/bundle-version: v1.2.0-dev
    gateway.networking.k8s.io/channel: experimental
  creationTimestamp: null
  name: tlsroutes.gateway.networking.k8s.io
spec:
  group: gateway.networking.k8s.io
  names:
    categories:
      - gateway-api
    kind: TLSRoute
    listKind: TLSRouteList
    plural: tlsroutes
    singular: tlsroute
  scope: Namespaced
  versions:
    - additionalPrinterColumns:
        - jsonPath: .metadata.creationTimestamp
          name: Age
          type: date
      name: v1alpha2
      schema:
        openAPIV3Schema:
          description: |-
            The TLSRoute resource is similar to TCPRoute, but can be configured
            to match against TLS-specific metadata. This allows more flexibility
            in matching streams for a given TLS listener.
            
            
            If you need to forward traffic to a single target for a TLS listener, you
            could choose to use a TCPRoute with a TLS listener.
          properties:
            apiVersion:
              description: |-
                APIVersion defines the versioned schema of this representation of an object.
                Servers should convert recognized schemas to the latest internal value, and
                may reject unrecognized values.
                More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
              type: string
            kind:
              description: |-
                Kind is a string value representing the REST resource this object represents.
                Servers may infer this from the endpoint the client submits requests to.
                Cannot be updated.
                In CamelCase.
                More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
              type: string
            metadata:
              type: object
            spec:
              description: Spec defines the desired state of TLSRoute.
              properties:
                hostnames:
                  description: |-
                    Hostnames defines a set of SNI names that should match against the
                    SNI attribute of TLS ClientHello message in TLS handshake. This matches
                    the RFC 1123 definition of a hostname with 2 notable exceptions:
                    
                    
                    1. IPs are not allowed in SNI names per RFC 6066.
                    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 TLSRoute, there
                    must be at least one intersecting hostname for the TLSRoute to be
                    attached to the Listener. For example:
                    
                    
                    * A Listener with `test.example.com` as the hostname matches TLSRoutes
                      that have either not specified any hostnames, or have specified at
                      least one of `test.example.com` or `*.example.com`.
                    * A Listener with `*.example.com` as the hostname matches TLSRoutes
                      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` and `test.example.net` would not match.
                    
                    
                    If both the Listener and TLSRoute have specified hostnames, any
                    TLSRoute hostnames that do not match the Listener hostname MUST be
                    ignored. For example, if a Listener specified `*.example.com`, and the
                    TLSRoute specified `test.example.com` and `test.example.net`,
                    `test.example.net` must not be considered for a match.
                    
                    
                    If both the Listener and TLSRoute have specified hostnames, and none
                    match with the criteria above, then the TLSRoute is not accepted. The
                    implementation must raise an 'Accepted' Condition with a status of
                    `False` in the corresponding RouteParentStatus.
                    
                    
                    Support: Core
                  items:
                    description: |-
                      Hostname is the fully qualified domain name of a network host. This matches
                      the RFC 1123 definition of a hostname with 2 notable exceptions:
                      
                      
                       1. 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.
                      
                      
                      Hostname can be "precise" which is a domain name without the terminating
                      dot of a network host (e.g. "foo.example.com") or "wildcard", which is a
                      domain name prefixed with a single wildcard label (e.g. `*.example.com`).
                      
                      
                      Note that as per RFC1035 and RFC1123, a *label* must consist of lower case
                      alphanumeric characters or '-', and must start and end with an alphanumeric
                      character. No other punctuation is allowed.
                    maxLength: 253
                    minLength: 1
                    pattern: ^(\*\.)?[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$
                    type: string
                  maxItems: 16
                  type: array
                parentRefs:
                  description: |+
                    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. For Services, that means the Service must either be in the same
                    namespace for a "producer" route, or the mesh implementation must support
                    and allow "consumer" routes for the referenced Service. ReferenceGrant is
                    not applicable for governing ParentRefs to Services - it is not possible to
                    create a "producer" route for a Service in a different namespace from the
                    Route.
                    
                    
                    There are two kinds of parent resources with "Core" support:
                    
                    
                    * Gateway (Gateway conformance profile)
                    * Service (Mesh conformance profile, ClusterIP Services only)
                    
                    
                    This API may be extended in the future to support additional kinds of parent
                    resources.
                    
                    
                    ParentRefs must be _distinct_. This means either that:
                    
                    
                    * They select different objects.  If this is the case, then parentRef
                      entries are distinct. In terms of fields, this means that the
                      multi-part key defined by `group`, `kind`, `namespace`, and `name` must
                      be unique across all parentRef entries in the Route.
                    * They do not select different objects, but for each optional field used,
                      each ParentRef that selects the same object must set the same set of
                      optional fields to different values. If one ParentRef sets a
                      combination of optional fields, all must set the same combination.
                    
                    
                    Some examples:
                    
                    
                    * If one ParentRef sets `sectionName`, all ParentRefs referencing the
                      same object must also set `sectionName`.
                    * If one ParentRef sets `port`, all ParentRefs referencing the same
                      object must also set `port`.
                    * If one ParentRef sets `sectionName` and `port`, all ParentRefs
                      referencing the same object must also set `sectionName` and `port`.
                    
                    
                    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.
                    
                    
                    Note that for ParentRefs that cross namespace boundaries, there are specific
                    rules. Cross-namespace references are only valid if they are explicitly
                    allowed by something in the namespace they are referring to. For example,
                    Gateway has the AllowedRoutes field, and ReferenceGrant provides a
                    generic way to enable other kinds of cross-namespace reference.
                    
                    
                    
                    ParentRefs from a Route to a Service in the same namespace are "producer"
                    routes, which apply default routing rules to inbound connections from
                    any namespace to the Service.
                    
                    
                    ParentRefs from a Route to a Service in a different namespace are
                    "consumer" routes, and these routing rules are only applied to outbound
                    connections originating from the same namespace as the Route, for which
                    the intended destination of the connections are a Service targeted as a
                    ParentRef of the Route.
                  
                  
                  
                  
                  

                  items:
                    description: |-
                      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:
                      
                      
                      * Gateway (Gateway conformance profile)
                      * Service (Mesh conformance profile, ClusterIP Services only)
                      
                      
                      This API may be extended in the future to support additional kinds of parent
                      resources.
                      
                      
                      The API object must be valid in the cluster; the Group and Kind must
                      be registered in the cluster for this reference to be valid.
                    properties:
                      group:
                        default: gateway.networking.k8s.io
                        description: |-
                          Group is the group of the referent.
                          When unspecified, "gateway.networking.k8s.io" is inferred.
                          To set the core API group (such as for a "Service" kind referent),
                          Group must be explicitly set to "" (empty string).
                          
                          
                          Support: Core
                        maxLength: 253
                        pattern: ^$|^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$
                        type: string
                      kind:
                        default: Gateway
                        description: |-
                          Kind is kind of the referent.
                          
                          
                          There are two kinds of parent resources with "Core" support:
                          
                          
                          * Gateway (Gateway conformance profile)
                          * Service (Mesh conformance profile, ClusterIP Services only)
                          
                          
                          Support for other resources is Implementation-Specific.
                        maxLength: 63
                        minLength: 1
                        pattern: ^[a-zA-Z]([-a-zA-Z0-9]*[a-zA-Z0-9])?$
                        type: string
                      name:
                        description: |-
                          Name is the name of the referent.
                          
                          
                          Support: Core
                        maxLength: 253
                        minLength: 1
                        type: string
                      namespace:
                        description: |-
                          Namespace is the namespace of the referent. When unspecified, this refers
                          to the local namespace of the Route.
                          
                          
                          Note that there are specific rules for ParentRefs which cross namespace
                          boundaries. Cross-namespace references are only valid if they are explicitly
                          allowed by something in the namespace they are referring to. For example:
                          Gateway has the AllowedRoutes field, and ReferenceGrant provides a
                          generic way to enable any other kind of cross-namespace reference.
                          
                          
                          
                          ParentRefs from a Route to a Service in the same namespace are "producer"
                          routes, which apply default routing rules to inbound connections from
                          any namespace to the Service.
                          
                          
                          ParentRefs from a Route to a Service in a different namespace are
                          "consumer" routes, and these routing rules are only applied to outbound
                          connections originating from the same namespace as the Route, for which
                          the intended destination of the connections are a Service targeted as a
                          ParentRef of the Route.
                          
                          
                          
                          Support: Core
                        maxLength: 63
                        minLength: 1
                        pattern: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?$
                        type: string
                      port:
                        description: |-
                          Port is the network port this Route targets. It can be interpreted
                          differently based on the type of parent resource.
                          
                          
                          When the parent resource is a Gateway, this targets all listeners
                          listening on the specified port that also support this kind of Route(and
                          select this Route). It's not recommended to set `Port` unless the
                          networking behaviors specified in a Route must apply to a specific port
                          as opposed to a listener(s) whose port(s) may be changed. When both Port
                          and SectionName are specified, the name and port of the selected listener
                          must match both specified values.
                          
                          
                          
                          When the parent resource is a Service, this targets a specific port in the
                          Service spec. When both Port (experimental) and SectionName are specified,
                          the name and port of the selected port must match both specified values.
                          
                          
                          
                          Implementations MAY choose to support other parent resources.
                          Implementations supporting other types of parent resources MUST clearly
                          document how/if Port is interpreted.
                          
                          
                          For the purpose of status, an attachment is considered successful as
                          long as the parent resource accepts it partially. For example, Gateway
                          listeners can restrict which Routes can attach to them by Route kind,
                          namespace, or hostname. If 1 of 2 Gateway listeners accept attachment
                          from the referencing Route, the Route MUST be considered successfully
                          attached. If no Gateway listeners accept attachment from this Route,
                          the Route MUST be considered detached from the Gateway.
                          
                          
                          Support: Extended
                        format: int32
                        maximum: 65535
                        minimum: 1
                        type: integer
                      sectionName:
                        description: |-
                          SectionName is the name of a section within the target resource. In the
                          following resources, SectionName is interpreted as the following:
                          
                          
                          * Gateway: Listener name. When both Port (experimental) and SectionName
                          are specified, the name and port of the selected listener must match
                          both specified values.
                          * Service: Port name. When both Port (experimental) and SectionName
                          are specified, the name and port of the selected listener must match
                          both specified values.
                          
                          
                          Implementations MAY choose to support attaching Routes to other resources.
                          If that is the case, they MUST clearly document how SectionName is
                          interpreted.
                          
                          
                          When unspecified (empty string), this will reference the entire resource.
                          For the purpose of status, an attachment is considered successful if at
                          least one section in the parent resource accepts it. For example, Gateway
                          listeners can restrict which Routes can attach to them by Route kind,
                          namespace, or hostname. If 1 of 2 Gateway listeners accept attachment from
                          the referencing Route, the Route MUST be considered successfully
                          attached. If no Gateway listeners accept attachment from this Route, the
                          Route MUST be considered detached from the Gateway.
                          
                          
                          Support: Core
                        maxLength: 253
                        minLength: 1
                        pattern: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$
                        type: string
                    required:
                      - name
                    type: object
                  maxItems: 32
                  type: array
                  x-kubernetes-validations:
                    - message: sectionName or port must be specified when parentRefs includes
                        2 or more references to the same parent
                      rule: 'self.all(p1, self.all(p2, p1.group == p2.group && p1.kind
                    == p2.kind && p1.name == p2.name && (((!has(p1.__namespace__)
                    || p1.__namespace__ == '''') && (!has(p2.__namespace__) || p2.__namespace__
                    == '''')) || (has(p1.__namespace__) && has(p2.__namespace__) &&
                    p1.__namespace__ == p2.__namespace__)) ? ((!has(p1.sectionName)
                    || p1.sectionName == '''') == (!has(p2.sectionName) || p2.sectionName
                    == '''') && (!has(p1.port) || p1.port == 0) == (!has(p2.port)
                    || p2.port == 0)): true))'
                    - message: sectionName or port must be unique when parentRefs includes
                        2 or more references to the same parent
                      rule: self.all(p1, self.exists_one(p2, p1.group == p2.group && p1.kind
                        == p2.kind && p1.name == p2.name && (((!has(p1.__namespace__)
                        || p1.__namespace__ == '') && (!has(p2.__namespace__) || p2.__namespace__
                        == '')) || (has(p1.__namespace__) && has(p2.__namespace__) &&
                        p1.__namespace__ == p2.__namespace__ )) && (((!has(p1.sectionName)
                        || p1.sectionName == '') && (!has(p2.sectionName) || p2.sectionName
                        == '')) || ( has(p1.sectionName) && has(p2.sectionName) && p1.sectionName
                        == p2.sectionName)) && (((!has(p1.port) || p1.port == 0) && (!has(p2.port)
                        || p2.port == 0)) || (has(p1.port) && has(p2.port) && p1.port
                        == p2.port))))
                rules:
                  description: Rules are a list of TLS matchers and actions.
                  items:
                    description: TLSRouteRule is the configuration for a given rule.
                    properties:
                      backendRefs:
                        description: |-
                          BackendRefs defines the backend(s) where matching requests should be
                          sent. If unspecified or invalid (refers to a non-existent resource or
                          a Service with no endpoints), the rule performs no forwarding; if no
                          filters are specified that would result in a response being sent, the
                          underlying implementation must actively reject request attempts to this
                          backend, by rejecting the connection or returning a 500 status code.
                          Request rejections must respect weight; if an invalid backend is
                          requested to have 80% of requests, then 80% of requests must be rejected
                          instead.
                          
                          
                          Support: Core for Kubernetes Service
                          
                          
                          Support: Extended for Kubernetes ServiceImport
                          
                          
                          Support: Implementation-specific for any other resource
                          
                          
                          Support for weight: Extended
                        items:
                          description: |-
                            BackendRef defines how a Route should forward a request to a Kubernetes
                            resource.
                            
                            
                            Note that when a namespace different than the local namespace is specified, a
                            ReferenceGrant object is required in the referent namespace to allow that
                            namespace's owner to accept the reference. See the ReferenceGrant
                            documentation for details.
                            
                            
                            <gateway:experimental:description>
                            
                            
                            When the BackendRef points to a Kubernetes Service, implementations SHOULD
                            honor the appProtocol field if it is set for the target Service Port.
                            
                            
                            Implementations supporting appProtocol SHOULD recognize the Kubernetes
                            Standard Application Protocols defined in KEP-3726.
                            
                            
                            If a Service appProtocol isn't specified, an implementation MAY infer the
                            backend protocol through its own means. Implementations MAY infer the
                            protocol from the Route type referring to the backend Service.
                            
                            
                            If a Route is not able to send traffic to the backend using the specified
                            protocol then the backend is considered invalid. Implementations MUST set the
                            "ResolvedRefs" condition to "False" with the "UnsupportedProtocol" reason.
                            
                            
                            </gateway:experimental:description>
                            
                            
                            Note that when the BackendTLSPolicy object is enabled by the implementation,
                            there are some extra rules about validity to consider here. See the fields
                            where this struct is used for more information about the exact behavior.
                          properties:
                            group:
                              default: ""
                              description: |-
                                Group is the group of the referent. For example, "gateway.networking.k8s.io".
                                When unspecified or empty string, core API group is inferred.
                              maxLength: 253
                              pattern: ^$|^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$
                              type: string
                            kind:
                              default: Service
                              description: |-
                                Kind is the Kubernetes resource kind of the referent. For example
                                "Service".
                                
                                
                                Defaults to "Service" when not specified.
                                
                                
                                ExternalName services can refer to CNAME DNS records that may live
                                outside of the cluster and as such are difficult to reason about in
                                terms of conformance. They also may not be safe to forward to (see
                                CVE-2021-25740 for more information). Implementations SHOULD NOT
                                support ExternalName Services.
                                
                                
                                Support: Core (Services with a type other than ExternalName)
                                
                                
                                Support: Implementation-specific (Services with type ExternalName)
                              maxLength: 63
                              minLength: 1
                              pattern: ^[a-zA-Z]([-a-zA-Z0-9]*[a-zA-Z0-9])?$
                              type: string
                            name:
                              description: Name is the name of the referent.
                              maxLength: 253
                              minLength: 1
                              type: string
                            namespace:
                              description: |-
                                Namespace is the namespace of the backend. When unspecified, the local
                                namespace is inferred.
                                
                                
                                Note that when a namespace different than the local namespace is specified,
                                a ReferenceGrant object is required in the referent namespace to allow that
                                namespace's owner to accept the reference. See the ReferenceGrant
                                documentation for details.
                                
                                
                                Support: Core
                              maxLength: 63
                              minLength: 1
                              pattern: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?$
                              type: string
                            port:
                              description: |-
                                Port specifies the destination port number to use for this resource.
                                Port is required when the referent is a Kubernetes Service. In this
                                case, the port number is the service port number, not the target port.
                                For other resources, destination port might be derived from the referent
                                resource or this field.
                              format: int32
                              maximum: 65535
                              minimum: 1
                              type: integer
                            weight:
                              default: 1
                              description: |-
                                Weight specifies the proportion of requests forwarded to the referenced
                                backend. This is computed as weight/(sum of all weights in this
                                BackendRefs list). For non-zero values, there may be some epsilon from
                                the exact proportion defined here depending on the precision an
                                implementation supports. Weight is not a percentage and the sum of
                                weights does not need to equal 100.
                                
                                
                                If only one backend is specified and it has a weight greater than 0, 100%
                                of the traffic is forwarded to that backend. If weight is set to 0, no
                                traffic should be forwarded for this entry. If unspecified, weight
                                defaults to 1.
                                
                                
                                Support for this field varies based on the context where used.
                              format: int32
                              maximum: 1000000
                              minimum: 0
                              type: integer
                          required:
                            - name
                          type: object
                          x-kubernetes-validations:
                            - message: Must have port for Service reference
                              rule: '(size(self.group) == 0 && self.kind == ''Service'')
                            ? has(self.port) : true'
                        maxItems: 16
                        minItems: 1
                        type: array
                    type: object
                  maxItems: 16
                  minItems: 1
                  type: array
              required:
                - rules
              type: object
            status:
              description: Status defines the current state of TLSRoute.
              properties:
                parents:
                  description: |-
                    Parents is a list of parent resources (usually Gateways) that are
                    associated with the route, and the status of the route with respect to
                    each parent. When this route attaches to a parent, the controller that
                    manages the parent must add an entry to this list when the controller
                    first sees the route and should update the entry as appropriate when the
                    route or gateway is modified.
                    
                    
                    Note that parent references that cannot be resolved by an implementation
                    of this API will not be added to this list. Implementations of this API
                    can only populate Route status for the Gateways/parent resources they are
                    responsible for.
                    
                    
                    A maximum of 32 Gateways will be represented in this list. An empty list
                    means the route has not been attached to any Gateway.
                  items:
                    description: |-
                      RouteParentStatus describes the status of a route with respect to an
                      associated Parent.
                    properties:
                      conditions:
                        description: |-
                          Conditions describes the status of the route with respect to the Gateway.
                          Note that the route's availability is also subject to the Gateway's own
                          status conditions and listener status.
                          
                          
                          If the Route's ParentRef specifies an existing Gateway that supports
                          Routes of this kind AND that Gateway's controller has sufficient access,
                          then that Gateway's controller MUST set the "Accepted" condition on the
                          Route, to indicate whether the route has been accepted or rejected by the
                          Gateway, and why.
                          
                          
                          A Route MUST be considered "Accepted" if at least one of the Route's
                          rules is implemented by the Gateway.
                          
                          
                          There are a number of cases where the "Accepted" condition may not be set
                          due to lack of controller visibility, that includes when:
                          
                          
                          * The Route refers to a non-existent parent.
                          * The Route is of a type that the controller does not support.
                          * The Route is in a namespace the controller does not have access to.
                        items:
                          description: "Condition contains details for one aspect of
                          the current state of this API Resource.\n---\nThis struct
                          is intended for direct use as an array at the field path
                          .status.conditions.  For example,\n\n\n\ttype FooStatus
                          struct{\n\t    // Represents the observations of a foo's
                          current state.\n\t    // Known .status.conditions.type are:
                          \"Available\", \"Progressing\", and \"Degraded\"\n\t    //
                          +patchMergeKey=type\n\t    // +patchStrategy=merge\n\t    //
                          +listType=map\n\t    // +listMapKey=type\n\t    Conditions
                          []metav1.Condition `json:\"conditions,omitempty\" patchStrategy:\"merge\"
                          patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`\n\n\n\t
                          \   // other fields\n\t}"
                          properties:
                            lastTransitionTime:
                              description: |-
                                lastTransitionTime is the last time the condition transitioned from one status to another.
                                This should be when the underlying condition changed.  If that is not known, then using the time when the API field changed is acceptable.
                              format: date-time
                              type: string
                            message:
                              description: |-
                                message is a human readable message indicating details about the transition.
                                This may be an empty string.
                              maxLength: 32768
                              type: string
                            observedGeneration:
                              description: |-
                                observedGeneration represents the .metadata.generation that the condition was set based upon.
                                For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date
                                with respect to the current state of the instance.
                              format: int64
                              minimum: 0
                              type: integer
                            reason:
                              description: |-
                                reason contains a programmatic identifier indicating the reason for the condition's last transition.
                                Producers of specific condition types may define expected values and meanings for this field,
                                and whether the values are considered a guaranteed API.
                                The value should be a CamelCase string.
                                This field may not be empty.
                              maxLength: 1024
                              minLength: 1
                              pattern: ^[A-Za-z]([A-Za-z0-9_,:]*[A-Za-z0-9_])?$
                              type: string
                            status:
                              description: status of the condition, one of True, False,
                                Unknown.
                              enum:
                                - "True"
                                - "False"
                                - Unknown
                              type: string
                            type:
                              description: |-
                                type of condition in CamelCase or in foo.example.com/CamelCase.
                                ---
                                Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
                                useful (see .node.status.conditions), the ability to deconflict is important.
                                The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
                              maxLength: 316
                              pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
                              type: string
                          required:
                            - lastTransitionTime
                            - message
                            - reason
                            - status
                            - type
                          type: object
                        maxItems: 8
                        minItems: 1
                        type: array
                        x-kubernetes-list-map-keys:
                          - type
                        x-kubernetes-list-type: map
                      controllerName:
                        description: |-
                          ControllerName is a domain/path string that indicates the name of the
                          controller that wrote this status. This corresponds with the
                          controllerName field on GatewayClass.
                          
                          
                          Example: "example.net/gateway-controller".
                          
                          
                          The format of this field is DOMAIN "/" PATH, where DOMAIN and PATH are
                          valid Kubernetes names
                          (https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names).
                          
                          
                          Controllers MUST populate this field when writing status. Controllers should ensure that
                          entries to status populated with their ControllerName are cleaned up when they are no
                          longer necessary.
                        maxLength: 253
                        minLength: 1
                        pattern: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*\/[A-Za-z0-9\/\-._~%!$&'()*+,;=:]+$
                        type: string
                      parentRef:
                        description: |-
                          ParentRef corresponds with a ParentRef in the spec that this
                          RouteParentStatus struct describes the status of.
                        properties:
                          group:
                            default: gateway.networking.k8s.io
                            description: |-
                              Group is the group of the referent.
                              When unspecified, "gateway.networking.k8s.io" is inferred.
                              To set the core API group (such as for a "Service" kind referent),
                              Group must be explicitly set to "" (empty string).
                              
                              
                              Support: Core
                            maxLength: 253
                            pattern: ^$|^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$
                            type: string
                          kind:
                            default: Gateway
                            description: |-
                              Kind is kind of the referent.
                              
                              
                              There are two kinds of parent resources with "Core" support:
                              
                              
                              * Gateway (Gateway conformance profile)
                              * Service (Mesh conformance profile, ClusterIP Services only)
                              
                              
                              Support for other resources is Implementation-Specific.
                            maxLength: 63
                            minLength: 1
                            pattern: ^[a-zA-Z]([-a-zA-Z0-9]*[a-zA-Z0-9])?$
                            type: string
                          name:
                            description: |-
                              Name is the name of the referent.
                              
                              
                              Support: Core
                            maxLength: 253
                            minLength: 1
                            type: string
                          namespace:
                            description: |-
                              Namespace is the namespace of the referent. When unspecified, this refers
                              to the local namespace of the Route.
                              
                              
                              Note that there are specific rules for ParentRefs which cross namespace
                              boundaries. Cross-namespace references are only valid if they are explicitly
                              allowed by something in the namespace they are referring to. For example:
                              Gateway has the AllowedRoutes field, and ReferenceGrant provides a
                              generic way to enable any other kind of cross-namespace reference.
                              
                              
                              
                              ParentRefs from a Route to a Service in the same namespace are "producer"
                              routes, which apply default routing rules to inbound connections from
                              any namespace to the Service.
                              
                              
                              ParentRefs from a Route to a Service in a different namespace are
                              "consumer" routes, and these routing rules are only applied to outbound
                              connections originating from the same namespace as the Route, for which
                              the intended destination of the connections are a Service targeted as a
                              ParentRef of the Route.
                              
                              
                              
                              Support: Core
                            maxLength: 63
                            minLength: 1
                            pattern: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?$
                            type: string
                          port:
                            description: |-
                              Port is the network port this Route targets. It can be interpreted
                              differently based on the type of parent resource.
                              
                              
                              When the parent resource is a Gateway, this targets all listeners
                              listening on the specified port that also support this kind of Route(and
                              select this Route). It's not recommended to set `Port` unless the
                              networking behaviors specified in a Route must apply to a specific port
                              as opposed to a listener(s) whose port(s) may be changed. When both Port
                              and SectionName are specified, the name and port of the selected listener
                              must match both specified values.
                              
                              
                              
                              When the parent resource is a Service, this targets a specific port in the
                              Service spec. When both Port (experimental) and SectionName are specified,
                              the name and port of the selected port must match both specified values.
                              
                              
                              
                              Implementations MAY choose to support other parent resources.
                              Implementations supporting other types of parent resources MUST clearly
                              document how/if Port is interpreted.
                              
                              
                              For the purpose of status, an attachment is considered successful as
                              long as the parent resource accepts it partially. For example, Gateway
                              listeners can restrict which Routes can attach to them by Route kind,
                              namespace, or hostname. If 1 of 2 Gateway listeners accept attachment
                              from the referencing Route, the Route MUST be considered successfully
                              attached. If no Gateway listeners accept attachment from this Route,
                              the Route MUST be considered detached from the Gateway.
                              
                              
                              Support: Extended
                            format: int32
                            maximum: 65535
                            minimum: 1
                            type: integer
                          sectionName:
                            description: |-
                              SectionName is the name of a section within the target resource. In the
                              following resources, SectionName is interpreted as the following:
                              
                              
                              * Gateway: Listener name. When both Port (experimental) and SectionName
                              are specified, the name and port of the selected listener must match
                              both specified values.
                              * Service: Port name. When both Port (experimental) and SectionName
                              are specified, the name and port of the selected listener must match
                              both specified values.
                              
                              
                              Implementations MAY choose to support attaching Routes to other resources.
                              If that is the case, they MUST clearly document how SectionName is
                              interpreted.
                              
                              
                              When unspecified (empty string), this will reference the entire resource.
                              For the purpose of status, an attachment is considered successful if at
                              least one section in the parent resource accepts it. For example, Gateway
                              listeners can restrict which Routes can attach to them by Route kind,
                              namespace, or hostname. If 1 of 2 Gateway listeners accept attachment from
                              the referencing Route, the Route MUST be considered successfully
                              attached. If no Gateway listeners accept attachment from this Route, the
                              Route MUST be considered detached from the Gateway.
                              
                              
                              Support: Core
                            maxLength: 253
                            minLength: 1
                            pattern: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$
                            type: string
                        required:
                          - name
                        type: object
                    required:
                      - controllerName
                      - parentRef
                    type: object
                  maxItems: 32
                  type: array
              required:
                - parents
              type: object
          required:
            - spec
          type: object
      served: true
      storage: true
      subresources:
        status: {}
status:
  acceptedNames:
    kind: ""
    plural: ""
  conditions: null
  storedVersions: null