Naming conventions#
The chart names its resources after the release, so that several releases can run in the same namespace.
The prefix is the release name, or fullnameOverride when it is set.
The name of each component is the prefix, followed by the component name.
Resource names#
Component |
Name |
Port |
|---|---|---|
Backend |
|
8080, named |
Backend director, headless |
|
8080 |
Frontend |
|
3000, named |
ZEO server |
|
8100, named |
Pack job |
|
|
HTTPRoute |
|
|
Ingress, Volto API |
|
|
Ingress, frontend or Classic UI |
|
|
PostgreSQL cluster |
|
5432 |
PostgreSQL read-write service |
|
5432 |
PostgreSQL credentials secret |
|
|
Varnish |
|
6081 |
The names of the PostgreSQL and Varnish resources follow the conventions of their charts.
When the release name already contains the name of the dependency, the resources use the release name alone, so that the name isn’t repeated.
Otherwise, the name is the release name followed by the dependency name, as in <release>-postgresql.
The prefix of the names of the chart resources, the release name or fullnameOverride, is cut at 44 characters, so that <prefix>-backend fits the 52 characters of a StatefulSet name, whose pods have a label with the name and a hash.
Labels#
The resources carry these labels:
Label |
Value |
|---|---|
|
the chart name and version |
|
the chart name, or |
|
the release name |
|
the |
|
|
|
the component: |
The selector labels of a component are app.kubernetes.io/name, app.kubernetes.io/instance, and app.kubernetes.io/component.
Virtual host paths#
The Zope virtual host paths of the backend requests use the site id of site.id, and the public hostname, scheme, and port of the routing.
For their format, see Routing.