Policies · Gateway
MeshGatewayInstance
Deployment and Service settings for a built-in gateway on Kubernetes.
Behaviour per target
Output: GatewayClass, MeshGatewayConfig
Converted to a GatewayClass named after the instance
(controllerName: gateways.kuma.io/controller) whose parametersRef points at a
MeshGatewayConfig carrying the instance spec (replicas, serviceType, tags).
Both are cluster-scoped, so neither the MeshGatewayConfig nor the parametersRef
has a namespace: Kuma marks a class whose parametersRef names a namespace as
InvalidParameters and ignores its Gateways.
tags["kuma.io/service"] is dropped from the MeshGatewayConfig, with a warning: Kuma
copies those tags onto the instance it creates for each Gateway, which must keep the
generated <gateway>_<namespace>_svc value.
Set gatewayClassName on your Gateways to this name and create them in the instance's
namespace; the converted MeshGateway does both automatically
when the kuma.io/service tags match.
No output kind.
Not converted: GatewayClass and MeshGatewayConfig do nothing on 3.0. The error
describes the replacement, a delegated gateway (a Deployment and Service you own):
exclude its listen ports from inbound redirection with
traffic.kuma.io/exclude-inbound-ports (Universal: kuma-dp --exclude-inbound-ports)
and annotate the Service kuma.io/ignore: "true". It carries over the replicas,
serviceType and tags the manifest holds. The original goes to _manual/.
Timeline
| Version | Change |
|---|---|
| 2.7 | Setting kuma.io/service in tags deprecated (forbidden from 2.9). |
| 3.0 | Removed with the built-in gateway API and its Kubernetes controllers. |
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.