Is it possible to pass the gateway class and httproute config within the values.yaml file?

[dilmikottahachchi]

Hi,
Is it possible for me to pass the gateway class config within the values.yaml file whilst doing the helm installation, instead of running it with the kubectl command sepearately.
helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.6.1 -n envoy-gateway-system --create-namespace

"The knowledge sources do not document any way to create GatewayClass and Gateway only by passing a values.yaml file to the Envoy Gateway Helm chart.

The official Helm docs describe configuring the controller (image, resources, controllerName, etc.) via values.yaml, but they do not mention a field like extraDeploy or any mechanism that would take arbitrary YAML in values.yaml and create GatewayClass/Gateway objects for you. [Helm values; Helm install]

All the examples that create GatewayClass and Gateway do so with separate manifests applied to the cluster (e.g., kubectl apply -f quickstart.yaml), not via Helm values. [Customize EnvoyProxy; TCP routing]

So, based on the provided docs:

There is no documented support for creating GatewayClass/Gateway purely by putting them into values.yaml.
The supported pattern is to install Envoy Gateway with Helm (optionally using values.yaml), and create GatewayClass/Gateway as separate Kubernetes manifests."

Help on this is much appreciated.

[zirain]

this's not supported, and won't be support in the near future.

IMO, it's not a good way to put everything in one chart.