Curious how Kubernetes seems to magically achieve your desired state? When you pass your YAML file to the Kubernetes API and stuff just happens, what is going on? Eric Shanks breaks down the basics of the control loop that Kubernetes uses to accomplish this.
Eric Shanks comments:
The mechanism that allows for Kubernetes to enforce this desired state is the control loop. The basics of this are pretty simple. A control loop can be though of in three stages.
Observe – What is the desired state of our objects?
Check Differences – What is the current state of our objects and the differences between our desired state?
Take Action – Make the current state look like the desired state.
Repeat – Repeat this over and over again.
This is just a high-level explanation, of course. For a deeper dive, read more at The IT Hollow Kubernetes – Desired State and Control Loops.
- VMware is Delivering Pipelines to the Cloud with CAS - November 19, 2019
- Ixia Brings Consistency to Visibility - November 15, 2019
- LogicMonitor Reveals the True Cost of IT Outages - November 5, 2019
- Do You Use GitHub? Ever Thought About Backup… - October 29, 2019
- LucidLink’s Clearly Different Approach to Object Storage - October 28, 2019
- Kubernetes Homelab With Raspberry Pi and K3sup - October 24, 2019
- Unpacking the IBM Red Hat Conundrum - October 23, 2019
- A Kind Way to Learn Kubernetes - October 18, 2019
- Why Are We Doing Kubernetes? - October 17, 2019
- NGINX Reminds Me of Bo Jackson - October 8, 2019