Cloud Native Computing Foundation Kubernetes Community Days (KCD) Africa 2022, 24 Jul 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Introduction to ArgoCD by Saiyam Pathak

Description

Saiyam Pathak, Director of Technical Evangelism at Civo & CNCF Ambassador introduces ArgoCD.

---
KCD Africa 2022 is the 2nd iteration of the Kubernetes Community Days Africa, a CNCF-powered free community event. Visit https://kcdafrica.com for more information.

A

It for some touchy, we have a guest speaker, sayam patak is he'll, be talking to us about github's, using aggro cd.

A

A

Yeah he'll be talking to us about ago cd guitar using ago cd he's the director of technical evangelism at sivo sam. Can you hear me welcome.

B

Yes, I can hear you. Can you hear me? Well, yes, and thank you very much for awesome, yeah glad to be here on kcb africa. um It's fantastic, fantastic event that you people are doing, I'm happy to be part of it. Okay, awesome! Thank you cool I'll present. My screen.

C

I hope you are able to see my screen.

A

Yes, I can see it.

C

B

Cool, so uh thank you for the introduction. My name is siam pattak and I am the director of technical evangelism at ceo, uh which is a next-gen cloud platform um providing kubernetes service and in this session I would like to tell you more about the argo project, the get ops principles, how we can use argo cd. uh We try to use the maximum benefit of this time, to show you hands-on demo as well, so that you get the max out of this so starting off with the argo project itself.

B

So argo is a cncf incubating project and argo um is able to do a lot of things, so people usually uh get confused in only the cd part, so argo do not have only the cd part. It has many more things uh that are. You know uh that are there so, like you have the cd obviously, which we'll be talking about for the githubs uh rollouts, which combines with the cd and gives you the complete workflow. Then you have specific workflow for running the machine.

B

Learning pipelines where you can create the workflows and the events that trigger uh on certain acts so workflows will orchestrate uh jobs on kubernetes, create and run workflows on k8, so you can you'll, be able to create and run your workflows, machine learning, workflows on and run them on communities again. The use cases mainly involve around the machine learning, batch processing, ci pipelines and each step. Obviously, each step in the workflow. So workflow you can say as a pipeline is there. There are multiple steps. Each step will be running as a container.

B

um Argo events are go. Events are like uh event based dependency manager for kubernetes variety of event. Sources can be there like pep hook, s3, uh we have a pub sub slack. So all these are there which can trigger the cades objects, and it is cloud events compliant another cnc project, rollouts its advanced capabilities. So when, when you are talking about argo cd and you combine the rollouts with it, it provides you with advanced capabilities like blue green canary.

B

Let's say you want a different version of your applications for your customer, but only weighted traffic, like only 30 percent of your of your you know, customers of your uh people who are using a website should be able to see the new version. You can do the weighted traffic traffic. Splitting category deployments um automated rollback custom metric queries. All the stuff can be uh done using the rollouts.

B

um So, let's move on to the argo cd before algo cd, I would like to tell you about the git ops stuff, which is there so.

B

Is basically these are the principles that lets you have everything defined in your git repository, uh so you have the true githubs I'll tell you like. I recently created a video on my youtube channel about the true gitoff's way and how I call it and how I define true git ops is where I am able to define my infrastructure as well in git, so we are moving towards the era where people are managing their infrastructure and application using git itself. We can do that and we can do that using rbo cd itself.

B

So you have your. um You know the keys nodes which are there, and this is github repositories, so you can have git repository and you can have infrastructure repository or a folder in that, and you can have your app folder in that your infrastructure folder will be having your infrastructure templates and the best way that I feel uh we you know um that is it's done.

B

Is we use something which is called crossplay, so crossplane is infrastructure as a code stuff that can be used that can be installed on the main cluster, so how you will be achieving the true gitoff's way? Let me just show you once.

B

So you have your git repositories, and this is your cable k8, its cluster, your kubernetes cluster. In your kubernetes cluster. You will be installing argo cd and you will be installing cross play so uh arbo, cd and cross plane are over here now uh in crosstalk. Obviously, you will be having some providers that you have installed uh that will be provisioning, your kubernetes cluster or your resources on that particular cloud vendor each cloud vendor have their own cross plane provider. So you have installed a cross plane cross plan provider.

B

You have installed argo cd, argo cd is monitoring your git repository. So this is your git and it is monitoring your infra folder and your app folder.

B

So as soon as you deploy a file which crossplane understands it will deploy and crossplane controller will take that changes and will actually spin up your infrastructure and you can use something called application set, which is another cool crd custom resource from argo cd and you can create application set. You can connect this cluster to argo server and as soon as this is connected, your application will be deployed. I know it sounds complex and we haven't yet understood the uh cd, but I just wanted to tell you that you can have your infra.

B

You can have your infra and your applications in dub repositories and you can achieve the true github's way from argo cd from tools like rbo cd. That helps you do that monitoring the depository lives within kubernetes cluster.

B

So let's continue our journey with argo cd so where we were.

B

Yeah, so the problem it solves is very clear. I told you um you: can you have git, you can build, you can push now. This comes under the ci pipeline this this is there, but what about the deployment? You cannot use the same ci pipelines to deploy to kubernetes. If you deploy to kubernetes, how will you get the status of that, whether that application is deployed? How do you deploy the revisions for that applications? How do you manage those applications when something goes wrong? Does it notify you?

B

So all those things are not part of the ci stuff which is there so for deployment it is git, ops is needed and git ops is needed. uh You cannot do with regular pipelines with cube cdl apply, you will you need custom scripts, which you need hates access, cube, config files uh and also what about the monitoring? You have to write another custom script for that, so we cannot do all these for sure. That's why there are solutions and one of the solutions, one of the most popular solutions out. There is argo cd.

B

Now argo cd is built for kubernetes and github's approach. uh So the the very uh you know famous pipeline example that I always give I personally use it is. I have ci, I have data actions already there. So if any changes to my git repository, my github actions will be building the code, pushing it to uh the repository and changing my deployment file image in the repository itself, and then it will be. uh Then rbo cd will be deployed onto a kubernetes cluster. That will be monitoring the changes.

B

So rbo cd is there on the cluster and it will be deploying those uh taking all the changes and then it will be able to deploy your application onto a particular node which is there. So I think um all the benefits are very, very clear. Like you, you have the true tops approach. You have easy, packable easy roll backs. You can have your dr setups. You can actually have your complete infra and apps as part of your git repository. Something goes wrong. You exactly can create a replica of your cluster in a new environment.

B

That's the power of argo cv. uh You have single sso multi-cluster, uh you that's! That's where I was telling you about sorry, that's where I was telling you about the application set, so you can use the application for multi-cluster deployments uh all the clusters that are connected to argo cd.

B

If you have an application set application that particular application will be deployed across the cluster various use cases. For that you can, you know, let's say you have 100, you know many developers that join your organization and you want to spin up uh customer on daily basis with some set of uh deployments, hardened policies and all that stuff.

B

So you can have a github repository you can have application set created for that you can connect your new clusters to argo cd and automatically your cluster will be ready with the applications that you need for your new developers and they can access it. They can, you know, do that stuff same approach can be used for dr same approach can be used for deploying one fix application to all the clusters, so many use cases over there. It has a very fancy web ui.

B

So basically, it is device enough to do everything uh with respect to you know, uh management of um your git repositories, seeing the status thing, the health of your deployments, which are there and cli, is also there. So always argo cdcli will be there. Argo cli that you can use to you know, create and manage all your apps and you get the prometheus matrix out of the box.

B

So argo, argo setup is a regular ha or core argo.

B

So you have your argo setup, which is you can have it as a regular setup or a highly available setup or a core argo core argo was fairly new, not super new, but it is fairly new, which gives you only the apt amount of argo installation working is pretty simple, uh so you have your controllers, uh you have repo server, you have kit and you have the api server, which is connected to the controller sync between the repository and api server repository is basically the cache which is getting maintained. So you can see.

B

Repo server maintains the internal cache of the repo um in the hm mode. The authentication is via dex and notification. Control is now part of argo cd and it started at argo, labs, yeah now, part of argo cv and triggers uh and templates.

B

You have the server, which is this one that has exposed a consume by the web ui. So web ui and argo cd use this to connect to this, and it does all the magic for you.

B

You have application controller uh that obviously uses ocd repo server to get the manifest and talks to the aps server and puts both of them in sync, so that your applications are actually in sync, uh then you have argo core, so this this is what I was telling you the new kind of project, which is there and um getting started with argo, no multi-tenancy uh if equities, are back only managing web cli easy transition from code to full largo. That also is supported yeah with arbor 2.3.

B

I think there were many improvements, including the images which is good and application set. uh Notifications were part of argo cd, which is again uh superb uh many improvements, bug fixes were always there. Sync and different sync and diff strategies are also there. So I think those were some of the cool features uh for, for you know, argo cd. um How much time do I have? I can do a demo.

B

I cannot hear you.

A

Yeah, I think you still have like 15 minutes. Okay, awesome.

B

So, let's move to the actual action which is there. Let me see if you are seeing the right screen yeah. So this is actually the cevo. um You know the dashboard, which is there from where I'll be provisioning a kubernetes cluster right in front of you. Everything is there. So, let's create a live cluster demo, okay, kcd.

B

And the everything as it is, except that from ci cd we will be installing rocd.

B

So let's create this particular. Oh, I haven't chosen the size, yet nothing fancy that I have done.

B

Till the time it is getting created, let me show you the github repository that I'll be using to deploy the application. I hope I have some application. uh Maybe I can use this and I can use the deploy folder for that yep can be done cool, so I'll watch the deploy folder of this repository. So this repository is nothing uh there's a deploy. Folder in this there is a hello.yaml file uh that is just deploying a particular uh yaml file.

B

Actually, if you want to see the source code also, it's pretty simple: it's a flask uh application, uh so a flask application that is listening on port 8080 and it um as soon as anything is deployed. So that was the actual flow that I was talking about. Github actions will run so this will be. You know, checking out docker push building the image, pushing it to my repository and changing the deploy hello dot, yaml file with the image tag. So every time any change is there. It will change this particular tag which is over here.

B

So it will add that sha to the image tag and all the changes. So that completes my cycle. Any change I make in the um in the templates or in the code like in the html any chain change I make it will directly be visible with the new uh deployment, because argo will be watching this folder and ci will be adding uh building this and adding the new image to hello, dot yaml file. So that is uh where, on a very high level that that particular stuff is so yeah.

B

We already have the nodes up and running uh and we'll be soon having the cube config file that I'll be using, and let me just fix my terminal as well, so that you don't see anything fancy running over there in the meanwhile, then I have to share my complete screen.

C

C

B

C

B

So cube conflict is there I'll download the cube config file.

B

And save it, and now I need to reshare my screen because I have to show you the terminal window.

B

I hope you are able to see the terminal window now.

B

uh Okay, so now we export the cube config.

C

Cube cdl, you get nodes oops.

B

Cool um so kcd africa cluster is up and running in front of you. uh That's nice uh cube cdl get pods hyphen a. Let me see if argo cd is getting installed on that yep, argo cd, you can see uh notification decks, um repo server application, controller server. uh They are, you know, getting installed slowly slowly and what we are going to do is we need a service or cube cdl get.

C

B

I think there will be a service, argo cd server. Let me just change that to a load, balancer.

C

You'll see the edit svc.

C

Rocd and make it.

C

Loads balancer.

B

I can definitely create the ingress. That's being lazy over here, you'll see I'll get.

C

Also for me, let me check again.

B

If stuff has been running, um yep most of the stuff is running, some are still you know getting ready and you see they'll get svc.

C

Let's try it out.

C

I think the pod is still getting ready. I'll go cd.

B

Yeah, so all the parts are running and you can see uh what all all the parts are. So you have repo server and we saw that in the diagram, the application controller, uh the rbo cd server itself, the core one, the decks for authentication. You have the application controller notification controller. So all the components are.

C

Over here I'm just trying to connect to the particular server.

B

Once it's done I'll definitely share the other window and in the meanwhile I'll also try to get.

C

B

So this is the initial secret for the argo cd ui cool. uh My argo cd is up and running. I can switch the screens now.

B

C

B

See my face again, uh let me share the window again.

B

So this is the screen. I proceed.

B

That's the same load balancer! You can see that our cd is up and running we'll copy, our password that I showed you how to get it and I think admin is the username.

B

This is your fancy argo cd uh ui, which is there. So this is how it looks like you can actually add a new app from here, a demo app and give you know uh sync policy automatic. uh You can prune the resources on deletion. You can self heal. You can also have auto, create namespace.

B

um All these you can do from here we'll give the url. Let's.

C

Go here, let's give the url.

C

And I think the branch is main so we'll give yeah. We main branch is fine and.

B

Path is deploy.

C

B

Destination is this cluster namespace? We can leave as it is and let's try to create it.

B

So you can see. uh This is how it starts the the project and uh it starts to sync the project, the github project, within that with that kubernetes cluster and try to see if that this path is there, it can it deploy. So you can see this is getting deployed demo and.

B

The namespace is missing. Let me create the namespace. I actually did do the auto creation of the namespace.

C

B

Let me just see what is happening in the.

B

C

I do see that the app is not here.

C

Okay, let's try it.

C

C

Name, space is missing. I do have a name space, I believe so.

C

C

Let's delete and give.

B

C

And I'll create a live app.

C

C

This one is showing green good signal.

B

Cool yep everything is deployed and cube. Cta will get parts. Let me check in my terminal as well. Yes, I can show you that it is running yep. We can actually see everything is everything is running so we'll do a cube, ct and get svc so that we can go to that particular uh ip. So this is the node port, the services notebook.

B

C

Cluster ip and we can.

C

Pod is running and the cluster id is correct. Three one, six.

C

So I think we should be able to see the application soon.

B

So it you can see what all stuff it created. It created a service, it created a deployment and we can even go to that deployment. We can see it is synced. We can see what all stuff got deployed over here which application got deployed. So this was the image that is deployed, and this is the service node port service type, node port, which is 31692 and the.

C

Endpoint yep everything looks fine.

C

Let me just see oops.

C

It is somehow waiting, I hope, I'm in the right cluster. Yes, I am oh.

B

Yeah, just a second because I didn't firewalls.

B

Let me just for now, but don't do this, I'm adding.

C

Allowing everything.

B

Yep so yeah this is kcd chennai, but we can definitely change this to kcd africa. So, if, like I can show you the true github stuff, which is there so this is kcd. Welcome to kcv.

C

Africa and kcv africa.

B

And let's commit this so as soon as I commit the changes, what it will do is it will trigger um a pipeline over here and we can see. This is the github actions. I just hope my credentials are working fine in this particular repository, because I keep on changing them. So if it's not, then we will skip the credentials, part and uploading it.

B

The only part which will be deploy the docker image. So if it can deploy the docker image and push to my repository, then we can see the change else. It won't work as it is.

B

It says that the login is succeeded, so we might be able to see the stuff which is there and as soon as what will happen now is it will. It is checking deploy folder so very soon our git will be able to commit the deploy folder over here.

B

Let's see the details.

B

Till which step it is there.

B

It is push and deploy to the local repo yeah. Now now the push is happening to the local repo and it is completed perfect. So this is completed. uh Our deploy, folder got changed. Now, let's go back here. Let's see.

B

When it will get synced, I think 30 seconds is the sink.

B

Let's refresh yep, something is getting changed, so you can see it is getting changed. I can check in the terminal myself, you won't be able to see in the terminal, but yes, there is a new container which is getting created in the terminal. You have to believe me.

B

Yep it's running and yay. We are welcome to kcd africa and I hope you enjoyed the github's uh knowledge about arbor cd, how to connect a live demo, kcd, africa and uh one last thing that I would like to just add that I also have a community called cube, simplify that's the kind of community that I you know simplifying cloud native for everyone, and recently I started a new initiative called workshops which are free of cost, uh so two workshops are up uh which will be live on 11th and 18th of july.

B

Please feel free to register for them. uh Cubesimplifier.Com workshops is the link, and I really hope you enjoyed this particular demo on argo cd. So if you have any queries regarding argo cd regarding um any of the stuff that um you know, I am doing with respect to cube, simplify my youtube, my twitter, you can contact me anywhere and uh make sure to kind of follow me on social media as well. uh One question I just saw that just to confirm: did you tag your image with latest?

B

No, so it's not the latest, it's actually with the git commit, so it if you just see in my github actions in the workflows, I'm actually using the commit sha to tag the image with. I think somewhere.

C

Somewhere here, where it is yeah.

B

This one so I'm getting this particular uh sha shot and it will tag the image with that.

B

Cool yeah, I'm also there on the kcd africa slack uh so make sure you join that. If you have any questions uh you feel free to. Let me know, and I would be happy to answer all your queries as well. um Thank you so much for having me it was so I hope you enjoyed the session.

A

Awesome, thank you very much uh and thank you very much for hopping in last minute and uh saving the day. I think we have one more question: how did you update the image tag in your manifest file by john.

B

Can you can you bring back my uh uh my term, my uh yeah, so how it is happening is as soon as I commit. I have a github actions which is written, so github actions will run this file and it will create it will build the code, so docker file is there in the code. It build the code and I am using a ginger template.

B

So you can see this generate, deploy manifest from the ginger template. I am using the ginger template and the output file will be deploy hello, dot, yaml, so deploy hello, dot, yaml git, my git itself is committing to that. uh Just variable will be this image deploy tag, so you can see in the in the repository tmpl, hello, dot, a2.

B

This is the deploy tag, so that will be changed with the git commit, and this will be then post to deploy hello dot and that's how my image gets changed with the latest commit and arbo cd is watching this particular file uh deployment deploy hello.yaml. It will automatically get deployed onto your kubernetes cluster with the latest revision. That is that, so that's the magic and the power of uh git ops. Argo cd using it the right way, so I've shown you actually the complete cicd process till the deployment from the code.

B

Cool glad you understood.

B

uh I'm not able to hear you.

A

Sorry I met myself uh once again. Thank you very much and uh we look forward to more collaborations with you.

B

For sure for sure, uh thank you so much for having me awesome.