Technical Context

The technical context of the Pandur cluster.
Figure 1. The technical context of the Pandur cluster.
Motivation

This diagram shows the technical building blocks the cluster depends on or exposes, and which protocols connect them: HTTPS ingress from the internet, OIDC for every login, S3/CIFS for persisted or backed-up data, and Git for the desired state pulled by Argo CD.

Mapping

  • Traefik terminates all inbound HTTPS traffic behind the Hetzner Load Balancer; see networking.

  • Argo CD is the GitOps engine reconciling every other building block from this Git repository; see argocd.

  • External Secrets Operator and Secrets Store CSI Driver bridge Bitwarden Secrets Manager into native Kubernetes secrets; see security.

  • CloudNativePG + Barman Cloud Plugin operate PostgreSQL clusters and back them up to S3-compatible object storage; see cnpg-system.

  • csi-driver-smb / hcloud-csi provide CIFS-backed and Hetzner block storage volumes; see storage.

  • Prometheus, Grafana and Headlamp provide observability and a Kubernetes dashboard, both behind Keycloak SSO; see observability.