Explaining GitOps: How does it work?

[@xyvadimxy]

Easy and undestandble explanation. Thanks.

[@LawZist]

Great and simple explanation!

[@curious_kitten2355]

Vergy good explanation, i appriciate you effort , thanks :)

[@afroman1242]

Minor nit pick, Terraform isn't written in YAML, it's written Hashicorp Language (HCL)

[@DevOpsJourney]

True! Thanks

[@goikk6904]

Great vid!

[@Sureshdkannan1]

Do we have self healing option in case a particular pull has crashed the EKS containers or node?

[@DevOpsJourney]

@@Sureshdkannan1 deployments will test new images by only rolling out a percentage of the pods. If the new one doesn't come online it won't restart the others. You can also do auto rollbacks on canary deploys using something like ArgoROLLOUTS. I have a video on that of you are interested.

[@some-people-say]

Concourse had been doing that for ten years

[@DevOpsJourney]

Nice!

[@abdulshaikh6807]

Where to start to learn devops learning path

[@DevOpsJourney]

Hey there. Have you checked out the roadmap? Good to start with Linux/docker/GitHub/Jenkins kzbin.info/www/bejne/eoepdIp8rJdmopY

[@victornoagbodji]

The point made about security for the push vs pull model does not make sense. A firewall will be needed in both cases, regardless.

[@DevOpsJourney]

Hi there! Allowing traffic out is always easier than allowing traffic in. External CI/CD servers trying to push to a Kubernetes cluster will have a lot more security hoops to jump through then getting something like ArgoCD going. Hope this makes sense, and you're right I probably could of done a better job explaining the nuances of this in the video.