RFCs
Each design decision of Tack is an RFC in rfcs/, one subject each. An Active RFC is in force, and the code conforms to it. When the code and an RFC disagree, the RFC wins, and is amended first. This list is read from the RFCs when the site is built.
| RFC | Subject | Status | Version |
|---|---|---|---|
| RFC#0001 | Scope and Glossary | Active | 1.6 |
| RFC#0002 | The Engine and the Driver Interface | Active | 1.9 |
| RFC#0003 | The Ledger: Schema, Phases and Resuming | Active | 1.27 |
| RFC#0004 | CloudNativePG Support | Active | 1.14 |
| RFC#0005 | Flux Hold and Release | Active | 1.9 |
| RFC#0006 | The Git Change | Active | 1.8 |
| RFC#0007 | Break-Glass | Active | 1.15 |
| RFC#0008 | Confirming Routing from Strait's Status | Active | 1.4 |
| RFC#0009 | The CLI and its Dry Run | Active | 1.26 |
RFC#0001: Scope and Glossary
Tack moves a stateful workload's primary from one site to another, on the operator's command. This RFC sets what Tack does and what it does not do. It names Tack's parts and defines the terms the other RFCs use.
RFC#0002: The Engine and the Driver Interface
Tack is a generic engine plus one driver per workload type. A driver turns the workload's state into steps, written as data. The engine adds the hold, the Git change and the checks, then runs the steps in order. This RFC sets the driver interface, the step types, and the order in which the engine builds a plan.
RFC#0003: The Ledger: Schema, Phases and Resuming
Each run is a SiteFailover object (failover.tako.id/v1). Its spec holds the whole plan and a copy of the workload's configuration. Its status records each phase and each step before it starts and after it ends, with the values that later steps need. A run resumes from this object and from nothing else. The schema is Tack's contract with its users and with a future controller.
RFC#0004: CloudNativePG Support
The cnpg driver switches the primary of a CloudNativePG deployment in the distributed topology. In that topology, each site has one Cluster, .spec.replica.primary names the primary, and a demotion token moves the primary without losing writes. The driver also moves the read-write Pooler, which runs only at the primary's site. This RFC sets the steps, the signals Tack waits for, and the fields Tack writes to Git, each with the CloudNativePG fact behind it.
RFC#0005: Flux Hold and Release
Flux applies Git again over live changes. During a run, Tack holds only the objects the run changes. It annotates those live objects, so kustomize-controller skips them. Tack releases them only once Git equals live, with Git rendered the way Flux renders it. Tack then checks that Flux changed nothing.
RFC#0006: The Git Change
After the switch, Tack writes one commit to the GitOps repository, so that Git equals the live state. Tack does not know the repository's layout. The operator either maps each field to a file and a path, or lets Tack find the manifest that defines the object. The commit lands only on top of the revision that live matched when the run started.
RFC#0007: Break-Glass
A site loss can take Git down with it. Tack then still holds and switches the live objects, and the Git step waits until Git is back. Steps on a lost site wait for that site. If the site comes back and still answers as primary, the run stops until the operator approves fencing it. After the demotion of from, the run stops before each Failover step, the promotion of to included, while another site that answers is primary. This holds in every mode. Before the promotion, the run also stops while a value it captured, such as the demotion token, differs from its source. When a site answered its check and a read there then fails on a short network blip, the read is repeated, as the check is.
RFC#0008: Confirming Routing from Strait's Status
Strait routes each application name to the workload's active member, and follows a promotion on its own. When the Workload names Strait's objects, the last thing a run does is wait until Strait, at each listed site, routes to the new primary's member only. Tack reads Strait's status. It never writes Strait's objects.
RFC#0009: The CLI and its Dry Run
tack has six commands that act on runs: plan, the dry run; run, which starts a run once the operator confirms it; resume, which continues a run from its ledger; status, which reads ledgers; abandon, which marks a run that must never go on; and prune, which deletes the ledgers of old runs. A seventh command, completion, prints a shell completion script. The help, the man pages and the skill document for AI agents all come from one definition of the commands. A release builds the CLI's archives the same way each time from the same commit, and signs and attests what it publishes.