Epic information:

See https://istio.io/latest/docs/setup/additional-setup/gateway/ (under Kubernetes YAML)

Caveat: injection is disabled by default for the smcp namespace. This will need to change if we want users to use the injection mechanism for gateway creation.

From OSSM-1116:

Gateway injection works in a similar manner to sidecar injection, so all caveats that apply to sidecar injection will also apply to gateway injection, namely:

• Auto-injection is enabled by default upstream, but not by OSSM, which means users will need to add an injection label/annotation to the gateway deployment for injection to occur, when using OSSM defaults
• Injection is disabled in the SMCP namespace, which means that gateway injection will not occur for gateways deployed in the SMCP namespace.

From https://istio.io/latest/docs/setup/additional-setup/gateway/

Using auto-injection for gateway deployments is recommended as it gives developers full control over the gateway deployment, while also simplifying operations. When a new upgrade is available, or a configuration has changed, gateway pods can be updated by simply restarting them. This makes the experience of operating a gateway deployment the same as operating sidecars.