push model
An arrangement where a central machine sends changes out to the hosts when someone runs it, as Ansible does.
In more detail
Nothing changes until a person or a pipeline starts a run, so changes land while someone is watching. The costs are that the control node must be able to reach every host, and a host that is switched off during the run simply misses the change.
Related terms
- pull model — An arrangement where an agent on each host periodically asks a central server for its configuration and applies it.
- control node — The machine where Ansible is installed and where you run its commands; it reaches out to every other machine it manages.
- agent — A program that runs in the background on every managed machine, checking in with a central server and applying the configuration it is given.
- kubectl apply — The kubectl command that creates or updates Kubernetes objects to match the manifests you give it.
- GitOps — Operating a system by keeping its desired state in Git and letting a controller continuously make the live system match it.
Taught in
- Ansible Architecture And The Control Node — Ansible Configuration Management at Scale
- Twelve Keys To Production: Pulled Automatically — Certified GitOps Associate (CGOA) Exam Prep
- The Push Model vs. The Pull Model — Continuous Integration & Continuous Delivery Pipelines
References
- Ansible concepts
- ansible-pull: the pull mode Ansible also offers
- OpenGitOps principles
- kubectl apply reference