GitOps is the equivalent of a Kubernetes Controller
A Kubernetes Controller, which runs on the Kubernetes Control Plane, ensures that the observed state of the cluster matches the desired state
A thread 🧵
A Kubernetes Controller, which runs on the Kubernetes Control Plane, ensures that the observed state of the cluster matches the desired state
A thread 🧵
A Kubernetes Controller, which runs on the Kubernetes Control Plane, ensures that the observed state of the cluster matches the desired state
For example, the Deployment Operator (like a Deployment spec in a Kubernetes Manifest) watches fo ensure that all of the applications running as a Kubernetes Deployment are in the desired state
With GitOps, it’s doing the same thing except the source control repo (for example, a repo on GitHub) is using the repo as the Controller
The repo inside of source control tells Kubernetes “this is the desired state” and GitOps confirms that by looking at the repo
The repo inside of source control tells Kubernetes “this is the desired state” and GitOps confirms that by looking at the repo
• • •
Missing some Tweet in this thread? You can try to
force a refresh
