Policies · Gateway
MeshGatewayConfig
Built-in gateway deployment parameters referenced from a GatewayClass.
Behaviour per target
Output: MeshGatewayConfig
Copied unchanged when found in the input. Also emitted, cluster-scoped and without a namespace, from a MeshGatewayInstance conversion.
No output kind.
Copied to _manual/ (file labelled MANUAL), never to the apply tree, with a warning:
3.0 removes MeshGatewayConfig with the rest of the built-in gateway API, and the Helm
upgrade deletes the meshgatewayconfigs.kuma.io CRD and every object stored under it.
Carry its settings (replicas, service type, resources) over to the Deployment and Service
of the gateway you run. Listed under "Delete Before Upgrading to 3.0" with a
kubectl delete command (it is a cluster-scoped Kubernetes-only CRD, so never kumactl).
Timeline
| Version | Change |
|---|---|
| 3.0 | Removed with the built-in gateway API (meshgatewayconfigs.kuma.io CRD deleted). |
Related topics
- Gateways, Gateway API and GAMMA — The built-in gateway removal in Kuma 3.0, MeshGateway* to Gateway API, delegated gateways, and why MeshHTTPRoute and MeshTCPRoute stay.