After an emergency, an elections-office engineer edits binaries on the running production host so voters can keep checking polling locations. Why does that violate cloud-native build/release/run staging?
Select an answer to reveal the explanation.
Short Explanation
Build, release, and run are like stamp, label, and ship: once the package leaves the dock, you do not re-solder it on the truck. Editing binaries on the host erases the answer to “what is in prod?” Keep stages separate and releases immutable.
Full Explanation
Strict staging keeps an immutable build, combines it with environment config into a uniquely identified release, and runs only that release. Mutating binaries on a live host collapses those stages and makes provenance unanswerable. SSH capability myths and forbidding all config miss the methodological point. Pipeline product how-tos belong elsewhere.