Continuous reconciliationis another core GitOps principle. It means that software agents (operators or controllers) run loops that continuously observe the live system and compare it against the desired state declared in Git. If any divergence (drift) is found, the agentautomatically reconcilesthe system to match the declared configuration.
“Software agents continuously observe the actual system state and compare it with the desired state declared in Git. If a divergence is detected, the agents automatically reconcile the difference to bring the system back into alignment.â€
This providesautomation, consistency, and self-healing, which are hallmarks of GitOps.
[References:GitOps Principles (CNCF GitOps Working Group),Principle 4: Continuously reconciled.]
Question # 18
In GitOps, which option describesState Storemanagement?
A.
Storing state information in a relational database.
B.
Storing state information in a centralized database.
C.
Storing state information in a distributed file system.
D.
Storing state information in a version control system.
TheState Storeis typically implemented using aversion control system (VCS)such as Git. This ensures that the system’s state is auditable, versioned, and immutable. Other systems like databases or distributed file systems do not meet the immutability and versioning requirements of GitOps.
“In GitOps, the desired state must be stored in a version control system. This serves as the State Store, providing a complete, immutable, and auditable history of changes.â€
Thus, the correct answer isD: version control system.
[References:GitOps Terminology (CNCF GitOps Working Group)., ]
