CRD Gateway API (shturval-gateway-api-crds)
About the service
| Parameter | Description |
|---|---|
| GUI name | Gateway API module CRD |
| System name (identifier) | shturval-gateway-api-crds |
| Cluster Assignment | Installation of CRD Gateway API (GatewayClass, Gateway, HTTPRoute, GRPCRoute, etc.) to control traffic routing. |
| Critical | No |
| Public repository | Kubernetes Gateway API |
| Dependencies | — |
| Namespace | gateway-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.
Chart does not run the routing controller - it only supplies the CRD. Traffic processing is performed by the controller associated with the GatewayClass. In the Shturval platform, you can configure the installation of the Gateway API controller based on Cilium in the Cluster Network Management Module - see How to enable the Cilium controller.
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 missing, install it in the cluster: Available charts → chart shturval-gateway-api-crds → Install. When configuring the installation, create and 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, when installing the service, CRDs Gateway API stable version 1.4.1 is supplied.
| CRD | API group | API Version | Region | Version |
|---|---|---|---|---|
| BackendTLSPolicy | gateway.networking.k8s.io | v1 | Namespaced | Stable |
| GatewayClass | gateway.networking.k8s.io | v1 | Cluster | Stable |
| Gateway | gateway.networking.k8s.io | v1 | Namespaced | Stable |
| GRPCRoute | gateway.networking.k8s.io | v1 | Namespaced | Stable |
| HTTPRoute | gateway.networking.k8s.io | v1 | Namespaced | Stable |
| ReferenceGrant | gateway.networking.k8s.io | v1beta1 | Namespaced | Stable |
| TCPRoute | gateway.networking.k8s.io | v1alpha2 | Namespaced | Experimental |
| TLSRoute | gateway.networking.k8s.io | v1alpha3 | Namespaced | Experimental |
| UDPRoute | gateway.networking.k8s.io | v1alpha2 | Namespaced | Experimental |
| XBackendTrafficPolicy | gateway.networking.x-k8s.io | v1alpha1 | Namespaced | Experimental |
| XListenerSet | gateway.networking.x-k8s.io | v1alpha1 | Namespaced | Experimental |
| XMesh | gateway.networking.x-k8s.io | v1alpha1 | Cluster | Experimental |
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
| Parameter | Description | Type | Example |
|---|---|---|---|
metadata.name | Name ShturvalServicePatch | string | shturval-gateway-api-crds-experimental |
customvalues.experimental | true - experimental CRD set; false - stable (default) | boolean | true |
How to deploy this service - How to deploy a new service.