Business Context

The business context of the Pandur cluster and its GitOps repository.
Figure 1. The business context of the Pandur cluster and its GitOps repository.
Motivation

The cluster itself has no separate "business" outside of being the shared runtime platform for Kaiserpfalz EDV-Service and related organizations. The relevant business relationship is therefore between the people who operate/develop against the cluster and the external services it depends on.

Neighbors

  • Cluster Operator — maintains this repository, reviews and merges changes, is alerted if Argo CD reports a degraded state.

  • Application Developer — works in other repositories (e.g. gitops-paladins-inn, gitops-torg-codex, gitops-kaiserpfalz-edv) that are onboarded as additional Argo CD ApplicationSet sources via auto-applications.yml.

  • End User — uses the applications hosted on the cluster; authenticates via Keycloak SSO for anything requiring a login.

  • GitHub — hosts this repository and the sibling GitOps repositories; Argo CD polls/webhooks it as the source of truth.

  • Hetzner Cloud — infrastructure provider for compute, network, load balancer and block storage; Hetzner Robot/hidrive additionally provides CIFS storage used for backups.

  • Keycloak SSO — the single identity provider for the Kubernetes API, Argo CD, Grafana and Headlamp.

  • Bitwarden Secrets Manager — the external secret store consulted by the External Secrets Operator; no runtime secret is ever committed to Git.