Resources by scenario#
This page lists the resources that each scenario creates, as rendered by helm template with the chart’s values.
The names use the release name rel as an example, so <release> stands for the release name of your installation.
Resources created by the cnpg cluster chart and the varnish-cache chart are listed too, because the chart installs them.
Resources of each component#
Resource |
Created when |
|---|---|
StatefulSet |
always |
Service |
always |
Service |
always |
PodDisruptionBudget |
|
Deployment |
|
Service |
|
PodDisruptionBudget |
|
StatefulSet |
|
Service |
|
CronJob |
|
Job |
|
HTTPRoute |
|
Ingress |
|
Ingress |
|
Cluster |
|
Deployment |
|
The cluster chart also renders a ConfigMap and a test Job for the PostgreSQL cluster.
The PodDisruptionBudget of PostgreSQL isn’t rendered by the chart: the CloudNativePG operator creates it, when postgresql.cluster.enablePDB is true.
The PodDisruptionBudget of Varnish comes from the varnish-cache chart, when varnish.server.pdb.enabled is true.
Resources of each scenario#
Resource |
Default |
Classic UI with ZEO |
Volto with Varnish and ingress-nginx |
External PostgreSQL, no routing |
|---|---|---|---|---|
StatefulSet |
yes |
yes |
yes |
yes |
Service |
yes |
yes |
yes |
yes |
Service |
yes |
yes |
yes |
yes |
Deployment and Service |
yes |
no |
yes |
yes |
StatefulSet and Service |
no |
yes |
no |
no |
CronJob |
yes |
yes |
yes |
yes |
Job |
yes |
yes |
yes |
yes |
HTTPRoute |
yes |
yes |
no |
no |
Ingress |
no |
no |
yes |
no |
Cluster |
yes |
no |
yes |
no |
Varnish resources |
no |
no |
yes |
no |
The default scenario is Volto with PostgreSQL, which is what the chart renders with routing.gateway.name set.
The Classic UI with ZEO is How to install Plone with the Classic UI and ZEO.
The Volto scenario with Varnish and ingress-nginx is How to install Plone with Volto, PostgreSQL, and Varnish, with routing.type set to ingress-nginx.
The external PostgreSQL scenario is How to use an external PostgreSQL server, with routing.type set to none.