Moving from Ingress NGINX to Gateway API in Camunda 8.9

The Kubernetes Ingress NGINX controller that many teams rely on is reaching end of life in March 2026. For Camunda 8 self-managed users, this is important because Camunda’s Helm charts include an example Ingress configuration that targets Ingress NGINX, even though it is not enabled by default.

With Camunda 8.9, we are taking this opportunity to modernize our networking and align with the direction of the Kubernetes ecosystem by adopting Gateway API.

This post explains:

• What is changing in 8.9
• Why we won’t backport Gateway API to supported versions
• What options you have if you’re not ready to upgrade to 8.9 yet

Where we are today: Ingress NGINX in our Helm charts

Today, our self-managed Helm charts ship with a reference Ingress configuration wired for Ingress NGINX, which is not enabled by default.

# values.yaml
global:
...
  ingress:
    enabled: false
    external: false
    className: nginx

The Kubernetes project has announced the retirement of the Ingress NGINX controller in March 2026. For more background and the official details, see the Kubernetes blog post: Ingress NGINX Retirement: What You Need to Know.

Not all Ingress controllers are affected

It’s important to clarify that Ingress NGINX is one specific Ingress controller implementation, not the Ingress API itself. Other Ingress controllers are not being deprecated as part of this announcement.

What deprecation means in practice for Ingress NGINX

The retirement of Ingress NGINX means:

• No new releases, bug fixes, or security patches will be provided after March 2026.
• GitHub repository and installation artifacts are expected to remain available (Helm charts, container images) and existing deployments are expected to continue working.
• Running Ingress NGINX after retirement means accepting potential unpatched security and reliability risks.

What’s changing in Camunda 8.9: Gateway API by default

Starting with Camunda 8.9, we will:

• Replace the Ingress NGINX-based example with a Gateway API–based configuration.
• Treat Gateway API as the default and recommended way to expose Camunda 8 components when installing via Helm.

We have also provided a Gateway API Configuration Guide which can assist in configuration.

Why we are not backporting Gateway API

We will not be backporting Gateway API to supported versions of Camunda 8. Introducing Gateway API to existing versions would be a breaking change and goes against our backporting policy.

Instead, we are keeping those minor versions stable and focusing on Gateway API as a forward-looking improvement in 8.9.

If you’re not ready for 8.9 yet

We know not every team can jump to 8.9 immediately. Our documentation can help you configure Gateway API for supported Helm chart versions (8.6-8.8) if you want to adopt Gateway API without waiting for a full upgrade.

This guide focuses on practical configuration examples and decision points, rather than prescribing a single “correct” solution.

Summary

• The Ingress NGINX controller reaches end of life in March 2026.
• Camunda 8 Helm charts currently include an Ingress NGINX based example, though it is not enabled by default.
• Starting with Camunda 8.9, we will adopt Gateway API as the default way to expose Camunda when installing via Helm.
• We will not backport Gateway API support to 8.6–8.8, to avoid breaking changes in existing deployments. Instead, we provide a Gateway API configuration guide to help you:
  • Move away from Ingress NGINX on 8.6–8.8.
  • Adopt and operate Gateway API smoothly with 8.9.

If you’re operating Camunda 8 on Kubernetes today, now is a good time to:

• Take stock of where Ingress NGINX is used in your environment.
• Start planning your path to Gateway API or an alternative, using 8.9 and our configuration guide as key milestones.

For more information, please refer to the documentation or contact us.