Gateway API CRD versions
Overview
ACP maintains and installs the standard Gateway API custom resource definitions (CRDs) as part of the platform
lifecycle. The Envoy Gateway Operator manages Envoy Gateway extension CRDs in the
gateway.envoyproxy.io API group; it does not own the standard Gateway API CRDs in the
gateway.networking.k8s.io API group.
ACP uses the Gateway API CRDs from the Gateway API Experimental channel. This channel includes the standard Gateway API
resources and experimental Gateway API resources such as BackendTLSPolicy and ListenerSet.
Do not install a second Gateway API CRD bundle in an ACP-managed cluster. Use the CRDs provided by the ACP release when
creating or upgrading Gateway, Route, Policy, and ListenerSet resources.
ACP 3.16 was the first release with Gateway API CRDs. The version table below records the CRDs maintained by ACP for each release line.
ACP release mapping
Each release-line table lists one CRD per row. Type identifies whether the CRD comes from the Gateway API project or
Envoy Gateway. Version contains the served versions, Storage version contains the version used to persist the
resource, and Bundle version identifies the Gateway API CRD bundle. N/A means that the CRD is not part of the
Gateway API bundle.
ACP 3.16.x - 4.1.x
Changes:
- Gateway API CRDs are first introduced in ACP 3.16.
- This release line contains the initial standard Gateway API CRD set and no ACP Gateway API extension CRDs.
ACP 4.2.1 - 4.2.x
Changes:
- The Gateway API CRD bundle is updated to v1.3.0.
- Storage changes to
v1forGatewayClass,Gateway,GRPCRoute, andHTTPRoute. BackendTLSPolicyaddsv1alpha3and changes storage tov1alpha3.XBackendTrafficPolicyandXListenerSetare added.
ACP 4.3.x
Changes:
- The Gateway API CRD bundle is updated to v1.4.1.
BackendTLSPolicyadds servedv1and changes storage tov1.TLSRouteadds servedv1alpha3and changes storage tov1alpha3.XMeshis added.- Envoy Gateway CRDs are included as
v1alpha1resources.
ACP 4.4.x
Changes:
- The standard Gateway API CRD bundle is updated to v1.5.1.
ListenerSetis added.ReferenceGrantadds servedv1.TLSRouteadds servedv1and changes storage tov1.BackendTLSPolicyservesv1and uses it for storage.- Envoy Gateway CRDs remain at
v1alpha1.
For the configuration workflow, see Configure GatewayAPI Gateway, Configure GatewayAPI Route, and Configure GatewayAPI Policy.