The naming conventions for products are designed to increase consistency across documentation and between the development, staging and production deployments with the aim of increasing the usability of the build, test and deployment scripts.
EQB: European Question Bank
production- is used with
cluster to form the cluster name, e.g.
Workloads and services/ingress names generally follow the same pattern and are composed of two parts. The prefix is the lowercase product name abbreviation (e.g.
eqb-) or lowercase functional abbreviation (
monitoring-). The main part is the name of the component (e.g.
So the pattern looks like this
Namespaces are used to group the components of a product within a cluster, whist isolating them from components of other products. Namespaces are named for the product they contain, in the form of $product_name, e.g.
monitoring. So a cluster typically has multiple namespaces.
Clusters are named to reflect the various deployment environments. Simple names are used, using the template $environment-cluster. The cluster names chosen are:
Names of persistent volumes track the names of the tools that they serve using the template
Names of ConfigMaps and Secrets are of the form
Subdomains are in the form of
$subdomain.cessda.eu. The subdomain is not the same as the $product_name, i.e. for the CESSDA Data Catalogue the subdomain is
datacatalogue, whereas the $product_name is
For development and staging environments, the
-staging appended (e.g.