GatewayClassConditionAccepted - This condition indicates whether the GatewayClass has been accepted by the controller requested in the spec.controller field.

GatewayClassConditionReasonAccepted - This reason is used with the “Accepted” condition when the condition is true.

GatewayClassConditionReasonInvalidParameters - This reason is used with the “Accepted” condition when the GatewayClass was not accepted because the parametersRef field was invalid, with more detail in the message.

GatewayClassConditionReasonWaiting - This reason is used with the “Accepted” condition when the requested controller has not yet made a decision about whether to admit the GatewayClass.

GatewayConditionInSync - This condition is true when the Gateway has successfully synced externally.

GatewayConditionReady - This condition is true when the Gateway is expected to be able to serve traffic.

GatewayConditionReasonAddressNotAssigned - This reason is used with the “Ready” condition when none of the requested addresses have been assigned to the Gateway.

GatewayConditionReasonInSync - This reason is used with the “InSync” condition when the condition is true.

GatewayConditionReasonListenersNotReady - This reason is used with the “Ready” condition when one or more Listeners are not ready to serve traffic.

GatewayConditionReasonListenersNotValid - This reason is used with the “Ready” condition when one or more Listeners have an invalid or unsupported configuration and cannot be configured on the Gateway.

GatewayConditionReasonNoResources - This reason is used with the “Scheduled” condition when the Gateway is not scheduled because insufficient infrastructure resources are available.

GatewayConditionReasonNotReconciled - This reason is used with the “Scheduled” condition when no controller has reconciled the Gateway.

GatewayConditionReasonPodFailed - This reason is used when the underlying pod on the gateway has failed.

GatewayConditionReasonReady - This reason is used with the “Ready” condition when the condition is true.

GatewayConditionReasonScheduled - This reason is used with the “Scheduled” condition when the condition is true.

GatewayConditionReasonSyncError - This reason is used with the "InSync" condition when there has been an error encountered synchronizing the Gateway.

GatewayConditionReasonUnknown - This reason is used when the underlying pod has an unhandled pod status.

GatewayConditionScheduled - This condition is true when the controller managing the Gateway has scheduled the Gateway to the underlying network infrastructure.

ListenerConditionConflicted - This condition indicates that the controller was unable to resolve conflicting specification requirements for this Listener.

ListenerConditionDetached - This condition indicates that, even though the listener is syntactically and semantically valid, the controller is not able to configure it on the underlying Gateway infrastructure.

ListenerConditionReady - This condition indicates whether the Listener has been configured on the Gateway.

ListenerConditionReasonAttached - This reason is used with the “Detached” condition when the condition is False.

ListenerConditionReasonHostnameConflict - This reason is used with the “Conflicted” condition when the Listener conflicts with hostnames in other Listeners.

ListenerConditionReasonInvalid - This reason is used with the “Ready” condition when the Listener is syntactically or semantically invalid.

ListenerConditionReasonInvalidCertificateRef - This reason is used with the “ResolvedRefs” condition when the Listener has a TLS configuration with at least one TLS CertificateRef that is invalid or cannot be resolved.

ListenerConditionReasonInvalidRouteKinds - This reason is used with the “ResolvedRefs” condition when an invalid or unsupported Route kind is specified by the Listener.

ListenerConditionReasonNoConflicts - This reason is used with the “Conflicted” condition when the condition is False.

ListenerConditionReasonPending - This reason is used with the “Ready” condition when the Listener is not yet not online and ready to accept client traffic.

ListenerConditionReasonPortUnavailable - This reason is used with the “Detached” condition when the Listener requests a port that cannot be used on the Gateway.

ListenerConditionReasonProtocolConflict - This reason is used with the “Conflicted” condition when multiple Listeners are specified with the same Listener port number, but have conflicting protocol specifications.

ListenerConditionReasonReady - This reason is used with the “Ready” condition when the condition is true.

ListenerConditionReasonRefNotPermitted - This reason is used with the “ResolvedRefs” condition when one of the Listener’s Routes has a BackendRef to an object in another namespace, where the object in the other namespace does not have a ReferenceGrant explicitly allowing the reference.

ListenerConditionReasonResolvedRefs - This reason is used with the “ResolvedRefs” condition when the condition is true.

ListenerConditionReasonRouteConflict - This reason is used with the “Conflicted” condition when the route resources selected for this Listener conflict with other specified properties of the Listener (e.g.

ListenerConditionReasonUnsupportedAddress - This reason is used with the “Detached” condition when the Listener could not be attached to the Gateway because the requested address is not supported.

ListenerConditionReasonUnsupportedExtension - This reason is used with the “Detached” condition when the controller detects that an implementation-specific Listener extension is being requested, but is not able to support the extension.

ListenerConditionReasonUnsupportedProtocol - This reason is used with the “Detached” condition when the Listener could not be attached to be Gateway because its protocol type is not supported.

ListenerConditionResolvedRefs - This condition indicates whether the controller was able to resolve all the object references for the Listener.

RouteConditionAccepted - This condition indicates whether the route has been accepted or rejected by a Gateway, and why.

RouteConditionReasonAccepted - This reason is used with the "Accepted" condition when the condition is True.

RouteConditionReasonBackendNotFound - This reason is used when a Route references a backend with a supported kind but that does not exist.

RouteConditionReasonBindError - This reason is used when there is a generic binding error for a Route.

RouteConditionReasonConsulServiceNotFound - This reason is used when a Route references services that the controller cannot resolve as services inside of Consul.

RouteConditionReasonErrors - This reason is used when multiple resolution errors occur of varying types.

RouteConditionReasonInvalidKind - This reason is used when a Route references a backend with an unsupported group or kind.

RouteConditionReasonInvalidRouteKind - This reason is used when a Route is rejected from binding to a Listener because it does not match a Listener's allowed route kinds.

RouteConditionReasonListenerHostnameMismatch - This reason is used when a Route is rejected from binding to a Listener becasue it does not match a Listener's hostname.

RouteConditionReasonListenerNamespacePolicy - This reason is used when a Route is rejected from binding to a Gateway because it does not match a Listener's namespace attachment policy.

RouteConditionReasonRefNotPermitted - This reason is used with the “ResolvedRefs” condition when one of the Listener’s Routes has a BackendRef to an object in another namespace, where the object in the other namespace does not have a ReferenceGrant explicitly allowing the reference.

RouteConditionReasonResolvedRefs - This reason is used with the "ResolvedRefs" condition when the condition is True.

RouteConditionReasonServiceNotFound - This reason is used when a Route references Kubernetes services that the controller cannot resolve.

RouteConditionResolvedRefs - This condition indicates whether the controller was able to resolve all the object references for the Route.

GatewayClassAcceptedStatus - This condition indicates whether the GatewayClass has been accepted by the controller requested in the spec.controller field.

GatewayClassStatus - Defines the observed state of a GatewayClass.

GatewayInSyncStatus - This condition is true when the Gateway has successfully synced externally.

GatewayReadyStatus - This condition is true when the Gateway is expected to be able to serve traffic.

GatewayScheduledStatus - This condition is true when the controller managing the Gateway has scheduled the Gateway to the underlying network infrastructure.

GatewayStatus - Defines the observed state of a Gateway.

ListenerConflictedStatus - This condition indicates that the controller was unable to resolve conflicting specification requirements for this Listener.

ListenerDetachedStatus - This condition indicates that, even though the listener is syntactically and semantically valid, the controller is not able to configure it on the underlying Gateway infrastructure.

ListenerReadyStatus - This condition indicates whether the Listener has been configured on the Gateway.

ListenerResolvedRefsStatus - This condition indicates whether the controller was able to resolve all the object references for the Listener.

ListenerStatus - The status associated with a Listener.

RouteAcceptedStatus - This condition indicates whether the route has been accepted or rejected by a Gateway, and why.

RouteResolvedRefsStatus - This condition indicates whether the controller was able to resolve all the object references for the Route.

RouteStatus - The status associated with a Route with respect to a given parent.