Federico CoppedeandGitHub b4f2da2171 docs: Add Gateway API routing to Kubernetes deployment guide (#12168) ...

## Description
This PR updates the Kubernetes deployment documentation to address user
feedback regarding our routing instructions. A user noted that standard
`Ingress` is becoming outdated and requested configuration examples for
the modern Gateway API.

To support both existing and modern clusters, I have updated the guide
to provide two clear pathways for exposing ZITADEL.

## Changes Included
* **Prerequisites updated:** Mentioned Gateway API controllers alongside
standard Ingress controllers.
* **Refactored Stage 2 (Production):** Split the routing configuration
into "Option A: Standard Ingress" and "Option B: Gateway API".
* **Added YAML example:** Provided a sample `HTTPRoute` resource to
route traffic to the `zitadel` and `zitadel-login` backend services.
* **Terminology updates:** Broadened terms like "Ingress" to "Routing"
or "Routing controller" where applicable.

2026-05-18 20:03:27 +05:30

..

api

fix(oidc): use authenticated encryption for opaque tokens (#12017)

2026-04-13 10:59:50 +00:00

docs

docs: Add Gateway API routing to Kubernetes deployment guide (#12168)

2026-05-18 20:03:27 +05:30

login

fix(login): apply custom request headers from environment variable in proxy (#12144)

2026-05-12 08:34:39 +02:00