How to install Plone with Volto, PostgreSQL, and Varnish#
This guide shows you how to install the default scenario with a Varnish cache in front of the site. Varnish receives all the requests, and sends the ones it doesn’t cache to the backend or the frontend.
Prerequisites#
A Gateway API implementation, and a Gateway
Install#
helm install plone plone/plone --namespace plone --create-namespace \
--set varnish.enabled=true \
--set routing.hostname=plone.example.com \
--set routing.gateway.name=<gateway> \
--set routing.gateway.namespace=<gateway-namespace>
Replace <gateway> and <gateway-namespace> with the name and namespace of the Gateway that serves the site, and plone.example.com with its hostname.
The site is served over HTTP.
To serve it over HTTPS, see How to serve the site over HTTPS.
How it works#
Requests flow as follows:
/++api++: Gateway to Varnish, then to the backend pods, then to PostgreSQLeverything else, the pages and static assets of the site: Gateway to Varnish, then to the frontend pods
Varnish runs as a Deployment with one pod. To change what Varnish caches, see How to customize the Varnish VCL. For the default caching behavior, see Varnish.
Varnish can be added to any other scenario in the same way, with --set varnish.enabled=true.
With the Classic UI, also set --set varnish.ploneFrontend=false, see How to cache the site with Varnish.
This scenario, with ingress-nginx routing, is tested by ci/varnish-ingress-nginx-values.yaml.