How to route the site with ingress-nginx#
This guide shows you how to replace the Gateway API HTTPRoute with Ingress resources for the ingress-nginx controller. It works with any of the other scenarios.
[!WARNING] The ingress-nginx project was retired in March 2026, and gets no more releases or security fixes. Prefer Gateway API for new installations.
Prerequisites#
The ingress-nginx controller, installed in the cluster
The prerequisites of the scenario it’s combined with, except Gateway API
Install#
helm install plone plone/plone --namespace plone --create-namespace \
--set routing.type=ingress-nginx \
--set routing.hostname=plone.example.com
Replace plone.example.com with the hostname of the site.
The Ingress resources use the nginx IngressClass.
To use another one, set --set routing.ingressNginx.className=<class>.
Combine these values with the ones of any other scenario, for example --set varnish.enabled=true.
The site is served over HTTP. To serve it over HTTPS, see How to serve the site over HTTPS.
How it works#
With Volto, the chart creates two Ingress resources:
<release>-api:/++api++to the backend (or Varnish), rewritten to the Zope virtual host path with theuse-regexandrewrite-targetannotations<release>: everything else to the frontend (or Varnish)
With the Classic UI, it creates a single <release> Ingress, sending everything to the backend (or Varnish), rewritten to the Zope virtual host path.
For the details of these resources, see Routing.
Combined with Varnish, this scenario is tested by ci/varnish-ingress-nginx-values.yaml.