The plone Helm chart installs Plone 6 on Kubernetes.
A single chart covers the common ways to run Plone: with the Volto frontend or the Classic UI, on PostgreSQL or ZEO, with or without a Varnish cache, and with Gateway API or ingress-nginx routing.
The default installs Plone 6 with Volto, PostgreSQL, and Gateway API.
The documentation is published at plone.github.io/helm-charts, from the sources in docs.
It is organized by the Diátaxis framework:
- Tutorial: install Plone on Rancher Desktop, step by step.
- How-to guides: install each scenario, attach the site to a Gateway, serve it over HTTPS, cache it with Varnish, and more.
- Reference: the values, the components, and the resources of the chart.
- Explanation: the architecture, the storage choices, and the routing.
Helm 3.8 or later, and Kubernetes 1.29 or later, are required.
-
Install the CloudNativePG operator, which runs the PostgreSQL cluster of the default scenario:
helm repo add cnpg https://cloudnative-pg.github.io/charts helm upgrade --install cnpg cnpg/cloudnative-pg \ --namespace cnpg-system --create-namespace --wait -
Add the Plone Helm repository:
helm repo add plone https://plone.github.io/helm-charts helm repo update
-
Install Plone without routing, and open it with a port forward:
helm install plone plone/plone --namespace plone --create-namespace \ --set routing.type=none kubectl port-forward --namespace plone service/plone-frontend 3000:3000A Job creates the Plone site after the install, which takes a few minutes, and
helm installwaits for it. Then open http://localhost:3000.
Then change the password of the admin user.
To serve the site through a route instead, see Gateway API, or follow the tutorial.
With the default routing.type: gateway, the chart creates an HTTPRoute, attached to a Gateway that already exists in your cluster, set with routing.gateway.name.
The chart doesn't install the Gateway API CRDs, an implementation, or the Gateway.
See How to attach the site to a Gateway, and About Gateway API.
With routing.type: ingress-nginx, the chart creates Ingress resources for the ingress-nginx controller.
The ingress-nginx project was retired in March 2026, so this routing type is meant for clusters that still run it.
See How to route the site with ingress-nginx.
The how-to guides describe each combination of values that the chart supports, such as the Classic UI with ZEO, or an external PostgreSQL server. The scenarios can be combined, and the chart fails with an explanation when the values don't make sense together.
All the values are described in the values reference, and the default values are in charts/plone/values.yaml.
This chart replaces the charts that were previously in this repository. See How to migrate from the previous charts.
The chart is in charts/plone.
To install it from a checkout of this repository, add the repository of the CloudNativePG cluster chart, and fetch the dependencies:
helm repo add cnpg https://cloudnative-pg.github.io/charts
helm dependency update ./charts/plone
helm install plone ./charts/plone --values ./charts/plone/ci/default-values.yamlThe charts/plone/ci directory has a values file per tested scenario.
The GitHub Actions workflow lints and installs the chart with each of them, and test.sh does the same in a local cluster.
The documentation is built with Sphinx and MyST, with the theme of the Plone documentation, and checked with Vale. The tools are installed with uv:
make docs # build the HTML in docs/_build/html, warnings are errors
make docs-livehtml # rebuild on changes, at http://localhost:8050
make docs-vale # check the style and spelling
make docs-linkcheck # check the external linksWhen a change reaches main, the release workflow publishes the documentation to GitHub Pages, together with the index.yaml of the Helm repository, which chart-releaser keeps in the gh-pages branch.
Pull requests build and check the documentation without publishing it.