Learn how to implement continuous delivery for a Kubernetes cluster using ArgoCD. Includes deployment on AWS & automatic image updates.
Length 1:00:43
Captions English (Generated), Spanish (Auto-translated), French (Auto-translated), Korean (Auto-translated), Portuguese (Auto-translated), Vietnamese (Auto-translated) #argocd #kubernetes #gitops #helm #aws #eks #continuous-delivery #infrastructure-as-code #docker #cloud-computing
0:00 Hey everyone. Today, we're gonna take a look at Argo CD. 0:04 So Argo CD is a declarative GitOps continuous delivery 0:07 tool for Kubernetes. Essentially, what it's gonna allow us to do is it's 0:11 gonna allow us to define all of our infrastructure and 0:15 applications that run in a given Kubernetes cluster, and 0:19 define all of that in a YAML format that is Git 0:22 controlled. And then what we can do is we can set our 0:26 Kubernetes cluster to stay synced to that GitHub repo 0:30 so that whenever we push new changes to it, our Kubernetes cluster 0:33 automatically stays in sync with it. 0:36 And this is super useful because we can do things like, for example, 0:40 go ahead and I have a Kubernetes cluster right now that is 0:44 currently running Argo CD and has deployed a Redis cluster into 0:48 it. So you can see here, I'm getting pods in the Redis 0:51 namespace. So I have a Redis namespace, 0:55 and w- if I go ahead and just delete the namespace 0:59 Redis, for example, by accident, normally this might be a huge pain. 1:03 I'm gonna have to go ahead and set it all back up again. 1:08 However, now if I go ahead immediately after 1:10 deleting my Redis namespace 1:12 and get it again, you can see it's automatically reappeared 1:15 six 1:16 seconds ago. And if I look and see what's inside of it now, 1:20 well, we'll be amazed to find that we actually have new Redis pods 1:23 already starting 1:24 up. The reason why this is happening is because I've defined Redis 1:28 here as an application or a Helm chart that I'm 1:31 tracking in my Argo CD GitHub repository, 1:35 so my environment has detected a difference and is automatically 1:39 synchronizing to redeploy it. So Argo CD makes 1:42 managing Kubernetes clusters so much easier and really gives
The rest of the transcript is for members.
Sign in 