CRD Gateway API (shturval-gateway-api-crds)

About the service

ParameterDescription
GUI nameGateway API module CRD
System name (identifier)shturval-gateway-api-crds
Cluster AssignmentInstallation of CRD Gateway API (GatewayClass, Gateway, HTTPRoute, GRPCRoute, etc.) to control traffic routing.
CriticalYes
Quick installation groupCritical Services
Public repositoryKubernetes Gateway API
Dependencies—
Namespacegateway-system

Purpose

shturval-gateway-api-crds - CRD chart Gateway API. Deploys the gateway.networking.k8s.io API groups in the CRD cluster, necessary for working with GatewayClass, Gateway and Gateway API routes in the Shturval platform.

The chart does not run a routing controller. It only supplies the CRDs. Traffic is handled by the controller associated with a GatewayClass. The service is critical: it is installed on the management cluster and on client clusters. You do not enable the Load balancer group to get it. When the cluster serves HTTP traffic through Gateway API, the Cilium controller is already enabled. See Gateway API controller in Cilium.

When you connect a Gateway API controller to the cluster, make sure it supports the CRD version in the cluster. In Shturval 2.15 the shturval-gateway-api-crds chart supplies Gateway API CRDs version 1.6.1. The controller must support this version of the specification.

Where to configure

To check whether the CRD is installed or to change the configuration of an already installed service: cluster → Services and repositories → Installed services → find CRD of the Gateway API module (shturval-gateway-api-crds) → Manage.

If the service is not in the installed list, install it: Available charts → chart shturval-gateway-api-crds → Install. Select the namespace gateway-system.

After successful deployment of shturval-gateway-api-crds, the Gateway API resource configuration pages will become available in the GUI: in the Gateway Classes cluster, Gateways and in the Routes namespace. For more information about the Gateway API overview, see Gateway API.

More details in the documentation: Gateway API, Kubernetes Gateway API.


Deploy experimental version of CRD

By default, the service installs the stable Gateway API CRDs version 1.6.1.

CRDAPI groupAPI VersionRegionVersion
BackendTLSPolicygateway.networking.k8s.iov1NamespacedStable
GatewayClassgateway.networking.k8s.iov1ClusterStable
Gatewaygateway.networking.k8s.iov1NamespacedStable
GRPCRoutegateway.networking.k8s.iov1NamespacedStable
HTTPRoutegateway.networking.k8s.iov1NamespacedStable
ReferenceGrantgateway.networking.k8s.iov1beta1NamespacedStable
TCPRoutegateway.networking.k8s.iov1alpha2NamespacedExperimental
TLSRoutegateway.networking.k8s.iov1alpha3NamespacedExperimental
UDPRoutegateway.networking.k8s.iov1alpha2NamespacedExperimental
XBackendTrafficPolicygateway.networking.x-k8s.iov1alpha1NamespacedExperimental
XListenerSetgateway.networking.x-k8s.iov1alpha1NamespacedExperimental
XMeshgateway.networking.x-k8s.iov1alpha1ClusterExperimental

To deploy experimental CRDs, set the experimental: true parameter.

When installing the service

When setting the shturval-gateway-api-crds configuration in the Service Specification block, specify customvalues:

experimental: true

If the service is already installed

If the CRD of the Gateway API module (shturval-gateway-api-crds) is already deployed in the cluster, apply ShturvalServicePatch:

apiVersion: ops.shturval.tech/v1beta2
kind: ShturvalServicePatch
metadata:
  name: shturval-gateway-api-crds-experimental
spec:
  shturvalServiceConfigName: shturval-gateway-api-crds
  customvalues:
    experimental: true
ParameterDescriptionTypeExample
metadata.nameName ShturvalServicePatchstringshturval-gateway-api-crds-experimental
customvalues.experimentaltrue - experimental CRD set; false - stable (default)booleantrue

How to deploy this service - How to deploy a new service.