gateway-api-crds

gateway-api-crds

Kubernetes Gateway API CustomResourceDefinitions (standard and experimental channel)

TL;DR;

helm repo add christianhuth https://charts.christianhuth.de
helm repo update
helm install my-release christianhuth/gateway-api-crds

Introduction

This chart installs the Gateway API CustomResourceDefinitions on a Kubernetes cluster using the Helm package manager.

It tracks upstream releases and vendors both the standard and experimental channel CRD bundles, each as its own subchart. Enable exactly one of standard.enabled/experimental.enabled, and use that subchart's crds.* values to opt individual CRDs in or out.

Prerequisites

• Kubernetes 1.19+

Installing the Chart

To install the chart with the release name my-release:

helm repo add christianhuth https://charts.christianhuth.de
helm repo update
helm install my-release christianhuth/gateway-api-crds

These commands deploy the standard-channel Gateway API CRDs on the Kubernetes cluster in the default configuration. The Values section lists the values that can be configured during installation.

Tip: List all releases using helm list

Uninstalling the Chart

To uninstall the my-release deployment:

helm uninstall my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.

Note: Gateway API CRDs are cluster-scoped. Uninstalling this chart deletes the CRDs, which deletes every Gateway/HTTPRoute/etc. object cluster-wide. Set global.resourcePolicy.keep: true if you want helm uninstall to leave the CRDs in place.

Values

Key	Type	Default	Description
global.resourcePolicy.keep	bool	false	When true, adds the helm.sh/resource-policy: keep annotation to every CRD so helm uninstall (and rollbacks) won't delete them.
experimental.enabled	bool	false	Installs the experimental-channel Gateway API CRDs (includes everything in the standard channel plus newer, less stable resource kinds and fields).
standard.enabled	bool	true	Installs the standard-channel Gateway API CRDs. Enable exactly one of standard.enabled/experimental.enabled -- enabling both or neither fails the install with a clear error.
experimental.crds.backendtlspolicies	bool	true	Installs the BackendTLSPolicy CRD.
experimental.crds.gatewayclasses	bool	true	Installs the GatewayClass CRD.
experimental.crds.gateways	bool	true	Installs the Gateway CRD.
experimental.crds.grpcroutes	bool	true	Installs the GRPCRoute CRD.
experimental.crds.httproutes	bool	true	Installs the HTTPRoute CRD.
experimental.crds.listenersets	bool	true	Installs the ListenerSet CRD.
experimental.crds.referencegrants	bool	true	Installs the ReferenceGrant CRD.
experimental.crds.tcproutes	bool	true	Installs the TCPRoute CRD.
experimental.crds.tlsroutes	bool	true	Installs the TLSRoute CRD.
experimental.crds.udproutes	bool	true	Installs the UDPRoute CRD.
experimental.crds.xbackends	bool	true	Installs the XBackend CRD.
experimental.crds.xbackendtrafficpolicies	bool	true	Installs the XBackendTrafficPolicy CRD.
experimental.crds.xlistenersets	bool	true	Installs the XListenerSet CRD.
experimental.crds.xmeshes	bool	true	Installs the XMesh CRD.
standard.crds.backendtlspolicies	bool	true	Installs the BackendTLSPolicy CRD.
standard.crds.gatewayclasses	bool	true	Installs the GatewayClass CRD.
standard.crds.gateways	bool	true	Installs the Gateway CRD.
standard.crds.grpcroutes	bool	true	Installs the GRPCRoute CRD.
standard.crds.httproutes	bool	true	Installs the HTTPRoute CRD.
standard.crds.listenersets	bool	true	Installs the ListenerSet CRD.
standard.crds.referencegrants	bool	true	Installs the ReferenceGrant CRD.
standard.crds.tcproutes	bool	true	Installs the TCPRoute CRD.
standard.crds.tlsroutes	bool	true	Installs the TLSRoute CRD.
standard.crds.udproutes	bool	true	Installs the UDPRoute CRD.

Specify each parameter using the --set key=value[,key=value] argument to helm install.

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,

helm install my-release -f values.yaml christianhuth/gateway-api-crds