Day 0 and day 2
Six units started from a group somebody else's script created. This one builds one from an empty namespace — credentials, storage, node labels, and the certificate the CRD made mandatory back in Unit 6 — and then keeps it alive: rolling MySQL and the operator underneath live traffic without turning a Tuesday into an incident. It closes with the one page you actually keep: every default, reason string, promotion step and metric label set on a single screen, beside a dated appendix for the facts that will not stay true.
Topics
Unit test
Quick check: can you build a group from an empty namespace, design a certificate every client can verify against, and roll a MySQL upgrade without turning it into an incident?
Project
brprep — the day-0 pre-flight and the change plan
Write a shell pre-flight that reads a MysqlFailoverGroup manifest and reports what the API server will reject, what it will silently admit, and what an ordered update of it would actually do — so the first time anyone sees your production group's problems is before it is applied, not during an incident.