Managing clusters through files.
WHAT THE APPROACH IS
The repository describes the desired state, and a controller applies it.
WHAT THAT PROVIDES
A record of every change, with who and why The cluster matching a reviewable definition Rebuilding by pointing at the repository Drift corrected automatically
WHAT DRIFT IS
The cluster differing from the definition.
WHAT CAUSES IT
Changes made by hand.
WHAT THE CONTROLLER DOES ABOUT IT
Reverts them.
WHY THAT IS DESIRABLE
It enforces that the repository is the authority.
WHAT IT COSTS
A controller to operate Discipline, since direct changes stop working A slower path for urgent fixes
WHAT TO DO ABOUT URGENT FIXES
Agree a documented exception, applied and then committed.
WHY COMMITTED AFTERWARDS
Otherwise the controller reverts the fix.
WHAT TO KEEP IN THE REPOSITORY
Manifests Configuration References to images by digest or version
WHAT TO KEEP OUT
Secrets in plain text.
WHAT TO USE FOR THOSE
Encrypted files, or an external manager the cluster reads.
WHAT TO SEPARATE
Application code from deployment definitions, or accept coupling between them.
WHAT TO ESTABLISH
Who approves changes to the deployment repository.
