GitOps Without Pipelines With ArgoCD Image Updater

preview_player
Показать описание
Can we get rid of the part of CI/CD pipelines that are modifying GitOps manifests repositories with new releases? Can we use Argo CD Image Updater to streamline part of our processes?

#Argo #ArgoCD #GitOps #Kubernetes

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

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

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

▬▬▬▬▬▬ 🚀 Courses, books, and podcasts 🚀 ▬▬▬▬▬▬

▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Getting Rid Of Pipelines
01:09 Using Pipelines For CD
03:13 What Is Argo CD Image Updater?
04:06 Installing Argo CD Image Updater
06:29 Configuring ArgoCD Image Updater
09:55 Updating To The Latest Release
12:33 Declaring Versions And Ranges
16:58 Going Outside The Version Range
17:59 Pros And Cons
Рекомендации по теме
Комментарии
Автор

How do you update your manifests after building new releases?

IMPORTANT: For reasons I do not comprehend (and Google support could not figure out), YouTube tends to delete comments that contain links. Please exclude https:// from the links to ensure that your comments are not removed.

DevOpsToolkit
Автор

Depending on the CI Pipeline you could specify triggers on file changes in the GIT. For example: only build a new Docker Image when files have changed except the argocd manifest version file. This could prevent the loop.

wodan
Автор

Awesome vid! Looking into ArgoCD for work, and this is super timely. As always great content!👍

moardub
Автор

Great way to make your flow simple and GitOps. I am using this Addon approach in my current deployments. Love the way ArgoCD works.

amit.gadhia
Автор

Excellent Tutorial on argcd image updater. gratitude to you my friend. much appreciated !!

matk
Автор

Great content! So glad I found this channel.

wilcosec
Автор

Fantastic video. We might be using it since the looping disadvantage doesn't apply to us as we store our argocd manifests elsewhere. Thanks so much.

arpanchakraborty
Автор

Very cool! I was just starting to play with this one!

flakes
Автор

Great vid, and also quite funny. Thanks.

cubewhidden
Автор

you can use something like jenkins ignore committers to prevent the build loop.

mmesoto
Автор

Great video, thank you... please could you do a video about connecting argocd image updater to AWS Elastic container registry

Ibenyeugbala
Автор

What you think of this strategy?

1. CI pipeline builds new docker image in the app repo and push it to CR
2. CI(we are still in App build CI pipeline) knows image tag, it pull deployment repo, use kustomize to update image tag in deployment, update deployment repo, push it
3. ArgoCD watches for the deployment repo and notice the tag change
4. ArgoCD does the deployment

In here we use a single CI pipeline to build docker image, push it to CR, update deployment repo(which is a separate one) and let argo do the rest

kasvith
Автор

thank for this video, it's super awesome! small one from my side:
how would you suggest to organise image updater in case I have one argocd cluster and I have several environments(argocd projects) where I deploy my apps: dev, test, stage, prod.
I have app off apps for each env, but I want to have more control on what goes to production. thanks and again, good job!

VisibleToAnyone
Автор

Im currently condidering renovating our deployment processes and workflows for our Production environments. We're heavy ArgoCD users already and go down the autocommit kustomize changes to our repository (which I find flakey sometimes, but that could be our setup)

Would you still recommend Image Updater vs. this approach?

MegaMonkeH
Автор

Hi, you said that it supports Helm, Kustomize or native k8s Yaml.
But, it looks like they don't support native Yamls.
There were an open issue regarding this topic - :)
Thanks, great vidio!

nickbaum
Автор

Thank you for awesome content!
i have a question. there is no guide on official document how to link private google artifact registry. can i have some info about it?

sealuke
Автор

It's weird that it doesn't support ECR via IRSA out of the box. Instead, it looks like it actually integrates with aws-cli so it can use token-based creds.

joebowbeer
Автор

Gitlab has an option to avoid their internal CI to run upon a push, I think it was `-o ci.skip`. However, I'm not sure if it would work with any other but Gitlab's CI system .. and it also doesn't feel right.

JanChristophEbersbach
Автор

Very good!
Can argocd image updater work with aws ecr repository?

a
Автор

Hello, I am using ArgoCD for my deployments. Currently I am deploying applications to default project and SIT projects. Currently ArgoCD shows applications in all projects is there a way to select applications based on projects in UI

sarojinipriyanka