operators

The operators building block installs Kubernetes operators for stateful database workloads used by applications hosted on the cluster: MariaDB, Redis, and (as a nested app-of-apps) the CloudNativePG stack.

Applications inside the operators building block.
Figure 1. Applications inside the operators building block.
Application Chart / Source Namespace Purpose

mariadb-operator-crds

mariadb-operator-crds 25.8.3 (helm.mariadb.com/mariadb-operator)

operators

Custom Resource Definitions required by the MariaDB operator; installed as a separate release so CRDs and operator can be upgraded independently.

mariadb-operator

mariadb-operator 25.8.3 (helm.mariadb.com/mariadb-operator)

operators

Operator managing MariaDB custom resources for application repositories that need a MariaDB database.

redis-operator

redis-operator 0.21.2 (ot-container-kit.github.io/helm-charts)

operators

Operator managing RedisFailover/Redis custom resources for application repositories that need caching or a key-value store.

cnpg-system

Argo CD Application (app-of-apps), path: pandur/operators/cnpg-system/apps

argocd

Nested parent application reconciling the CloudNativePG stack; documented as its own Level 1 building block, see cnpg-system.
cnpg-system has no top-level pandur/apps/cnpg-system.yml entry of its own — it is bootstrapped as a child of operators. An earlier version of its Argo CD Application manifests referenced a non-existent path (see [TR-003 cnpg-system path typo]); this has since been corrected.
Bootstrap-only components

The kubelet CSR approver is still installed manually by create-pandur.sh during the initial bootstrap (before Argo CD exists), but is now also reconciled as an Argo CD Application; see security. The Hetzner Cloud Controller Manager followed the same pattern and has since been adopted into GitOps as well; see argocd ([TR-002 HCCM is not GitOps-managed], resolved).