Mastering Argo CD Sync Waves: A Deep Dive into Effective GitOps Synchronization Strategies

preview_player
Показать описание
Discover the ultimate control for your Kubernetes GitOps deployments with Argo CD's Sync Waves, Statuses, and Dry-Run features! 🌊⚙️

#argocd #kubernetes #gitops

▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬

▬▬▬▬▬▬ 💰 Sponsoships 💰 ▬▬▬▬▬▬

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬

▬▬▬▬▬▬ 🚀 Other Channels 🚀 ▬▬▬▬▬▬

▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Introduction to Argo CD dry-run, sync order, and statuses
03:26 Stateless Application With a Database
05:37 Create The Application, The Database Server, and The Schema
07:42 Argo CD Phases and Sync Waves
10:00 Argo CD Resource Statuses
12:13 Skip Argo CD Dry-Run
14:05 Resource Ordering With Argo CD
Рекомендации по теме
Комментарии
Автор

How do you orchestrate your orchestrators? 🤔

DevOpsToolkit
Автор

Man, you content is awesome. I am Devops engineer for years, and still find tons of very useful things in your videos. Thank you!

nzalex
Автор

YEAS! Finally I was given explanation how to make the sync waves are working. I've been dealing with it for half a year. Chicken/Egg issue solved ;-)

lukas-pastva
Автор

Great stuff as always !

Also: Yes, we need the schemahero replacement vid too !

PS: Whenever i see the Timoni thumbnail i read REPLAY CEMENT xD

microst
Автор

Thank you for sharing your experience - how would you address cache memory after changing ID and Passwords in an application through ArgoCD?

Fayaz-Rehman
Автор

Thanks for another great video 🎉 yes I am curious to know about the new upcoming misterious tool for the database schemas

IvanRizzante
Автор

hey @DevOpsToolkit, thank you very much for your content. Here's a small suggestion/request for future videos: with so many new technologies coming up periodically, could you create a video or maybe a series of videos that helps Kubernetes Administrators and/or architects to choose a set of recommended toolkit and tools for creating and managing a K8S cluster from SCRATCH? This could be based on specific use cases or company/team sizes, etc. Thanks for advance!

franpereyra
Автор

Interesting to see using hooks with timoni in ArgoCD which is like helm hooks 🎉

SiCrip
Автор

firstly, thank you for the awesome tutorials. Being said that I have a question, if a resource creation during the sync wave fails, would the other resource of sync wave rollback too along with the failed resource? if not then how we can achieve this so that there isn't a version drift in between the components of application upon failed upgrade.

aditya-iqcp
Автор

What about orchestrating using k8s native workflow tools like argo workflows or kubevela workflows?

geowalrus
Автор

these are edge cases... imo eventual consistency is the #1 solution. regarding the schema changes in particular, if one wanted to do them without downtime, aren't backwards compatible schema changes methodologies needed? ... and fully agree that schemahero should return a state... amazed they failed such basic stuff!

hugolopes
Автор

for the schema change, can't a readiness probe check if the required schema change was applied? just an idea... like that, one could deploy the app container before the schema change no?

hugolopes
Автор

I am new to GitOps, kubernetes, containers, etc and have been consuming yours and other's videos in an effort to get preview environments established for our developers. I seem to be having this very problem with ordering, but I'm using flux. Could you please cover how you would order and skip dry runs as related to flux?

CestMoi-rwzx
Автор

I don't think you mentioned ArgoCD's ApplicationSet in this video, but if you did, it would be worth mentioning that ApplicationSet doesn't currently obey sync waves on updates.

joebowbeer
Автор

Good video! Can we do inter application ordering as well. Cause from way i understand it pre-sync and post-sync are good annotations for objects belonging to same argocd application. But i was hoping to see waves to co-ordinate one argocd application dependency on another one.

RonakKogta
Автор

A better way of managing schema - is it Atlas? :D

pavelpikat
Автор

What is the best way to manage schema k8s style? Suck a cliffhanger!

invalidred
Автор

for somehow if a deployment failed, would previous version be deployed? so users can access it anyways

kasvith