Skip to content

Decision register

This register holds every decision about the cluster and the workloads on it, and every open question that blocks a decision. Long reasoning lives in linked research documents, not here.

  • Each area has one table of open questions and one table of decisions.
  • Identifiers have the form <area>-q<n> for a question and <area>-d<n> for a decision, for example idn-q1 and idn-d1. They are numbered per area and never reused.
  • A decision is written in the present tense, with the alternatives that were considered and a short rationale.
  • A decision has the status Proposed or Accepted. Only an Accepted decision is in force.
  • An answered question becomes a decision, and the question row keeps a pointer to that decision.
  • Changes go through issue → branch → pull request. Changing a decision’s status to Accepted in a merged pull request is what makes it official.
  • A decision is never deleted. To reverse one, change its wording and rationale. The Git history keeps the earlier versions.
AreaPrefixCovers
IdentityidnIdentity provider, accounts, single sign-on, secrets
PlatformpltCloud providers, Kubernetes, shared platform services such as databases
NetworknetIngress, DNS, TLS certificates
Data and backupdrBackups, restores, recovery objectives
EngineeringengRepositories, provisioning, images, ways of working such as this register
OperationsopsDeployment, upgrades, and changes to running systems
IDQuestion
idn-q1Does the identity provider run inside the customer cluster, or outside it, so that administrators can still log in when the cluster is down? Affects idn-d1 and the break-glass access to the cluster.
idn-q2Which tool manages secrets in a GitOps workflow: SOPS with Flux, External Secrets, or Sealed Secrets?
IDDecisionAlternativesRationaleStatus
idn-d1authentik is the identity provider, and Forgejo and Synapse sign in through it with OpenID ConnectKeycloak; Forgejo as the OAuth2 provider for Synapseauthentik maintains an official Helm chart and needs only PostgreSQL. See the authentik researchProposed
IDQuestion
plt-q1Which cloud providers do we offer to customers: Hetzner, Scaleway, OVHcloud, or a combination?
plt-q2Is Kubernetes managed by the provider, or self-run on virtual servers? Hetzner offers no managed Kubernetes, so this depends on plt-q1.
plt-q3Do authentik, Forgejo, and Synapse share one PostgreSQL cluster, or does each have its own? Sharing saves memory, but one failure affects all three.
IDDecisionAlternativesRationaleStatus
plt-d1The first test deployment runs on Hetzner Cloud in HelsinkiScaleway; OVHcloudLowest cost for a throwaway environment. It does not settle plt-q1. See src/opentofuProposed
plt-d2The CloudNativePG operator provides PostgreSQL, as a shared platform componentThe provider’s managed PostgreSQL; the bundled database in each Helm chartIt works the same on every provider, is declarative, and handles failover and backups. The bundled database in the authentik chart is for testing onlyProposed
IDQuestion
net-q1Which ingress or Gateway API controller does the cluster use?
net-q2Are DNS records managed by hand, or by external-dns?
IDDecisionAlternativesRationaleStatus
net-d1cert-manager issues public TLS certificates from Let’s EncryptCertificates issued by the provider or bought and installed by handThe common Kubernetes approach, with automatic renewal and no licence costProposed
IDQuestion
dr-q1What are the recovery point and recovery time objectives in the basic service, and where are backups stored?
IDDecisionAlternativesRationaleStatus
IDQuestion
eng-q1Are container images pulled from upstream registries, such as ghcr.io, or mirrored in a European registry?
IDDecisionAlternativesRationaleStatus
eng-d1Decisions and open questions are kept in this registerOne Architecture Decision Record (ADR) file per decisionOne shared source of truth. Decided in discussion #11 and implemented in issue #13Accepted
eng-d2OpenTofu provisions the infrastructureTerraform; the provider’s own toolsAn open-source, provider-neutral tool. Already used for the test deployment (plt-d1)Proposed
IDQuestion
IDDecisionAlternativesRationaleStatus
ops-d1Flux deploys the workloads from Git (GitOps)Argo CD; helm upgrade run by hand or from CIProposed in Deployment and operations. Flux is already in the dev containerProposed