The Second Principle of Version Control for Kubernetes Clusters

YAML is the way we define our Kubernetes cluster. And I can push that into which leads me to the second principle version control system, Git. So let's say you have all your code that you are maybe writing and updating on your laptop, you have a Git repo somewhere. Once you are done and you're happy, you did some local unit tests, you want to push it out, you do a Git push. You update your source control repository or your version control repository in Git,. Then you run, kick off a bunch of CI pipelines, like make sure that you do want to pause you there and say, um, what is the thing?