Everything you need to know about beginner guide to kubernetes.
[ad_1]Think about the difference between leaving a housemate a to-do list and writing them a contract. The to-do list says “buy bread on Monday, take out the bins Tuesday, water the plants Wednesday.”
It’s a sequence of instructions, and if any step fails or gets skipped, the whole thing fails. The contract says something different. It says the kitchen should always have bread, the bins should never overflow, and the plants should never go three days without water. One is a script. The other is a promise, and somebody has to keep checking whether the promise is being kept.
Kubernetes is what we get when that second approach is taken seriously and built into a whole infrastructure platform.
In this article, we will learn how Kubernetes is a system of promises, and that every piece of it is a small program keeping one of those promises.
[ad_2]
Source link
More on beginner guide to kubernetes
Stay tuned for updates on beginner guide to kubernetes as the story develops. Related: Migrating from Go to Rust.
Frequently Asked Questions
It compares leaving a housemate a to-do list with writing them a contract: a to-do list is a sequence of instructions that fails if any step is skipped, while a contract is a promise about what should always be true.
Because Kubernetes states promises about the desired state of infrastructure, and every piece of it is a small program continuously checking that the promise is being kept.
The guide explains Kubernetes as a system of promises, showing how each component keeps one of those promises.
A script is a sequence of steps that fails if one step fails, while Kubernetes declares the desired outcome and its components work to maintain it.
