GitLab Product Walk-Throughs - Ops Section, 29 Mar 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Ops Section Product Walk Through - Kubernetes Agent

Description

https://gitlab.com/gitlab-com/Product/-/issues/2190

A

Hey everybody: my name is kenny johnston. I'm a director of product here at gitlab, I'm going to be doing a walkthrough of our new um installation of our kubernetes agent. So let me go ahead and share my screen this one. Okay, um so just walk through. I was expecting to be able to set up the agent on gitlab.com did have to have my project authorized to be able to create agents, um or at least agent uh artifacts in the database. So I had that done before starting this discussion.

A

I figured I would just start with googling gitlab kubernetes agent set up and get started so uh gitlab kubernetes agent setup.

A

All right, so obviously I've been here before so here's gitlab kubernetes agent um can be good for integrating more secure, uh pull based with gitops engine all right. Okay, um here's how it works. Developer, pushes code that updates the repository and the manifest, and that manifests the agent is watching and pulling what's going on in that manifest. And then the configuration of the agent is in a potentially different location, getting started, uh install the agent server.

A

I have already done that because I'm using gitlab.com on github.com under cast.gitlab, okay, so I can skip that part. I don't need to install the cast okay, I need to define a configuration repository, so I created this example. Project called quantization to test and what did it say? Oops? I already have this hooked up. Let's stay over here define a configuration browser. Next, you need a gitlab repository to contain your agent configuration minimal. Repository, looks like this um that gitlab agents. Okay. So I'm going to name my agent.

A

Let's say I'm going to name it first agent, doculab agents, first agent, config diana okay. So, let's add a.

A

A

How many is this, and so I'm going to use the.

A

Same there was no template for me to use here. That would be cool if there was a template.

A

A

I need to pass this project, which was.

A

Okay lab examples, slash kubernetes agent test. You spell that right, yes, okay and then add agent.

A

A

So right now, so this is saying the configuration for the agent when it gets figured is hey. Where should I look for manifest projects? I'm going to look at myself? This is this same project, so got that part done back to instructions, create an agent record in gitlab. Next, create a gitlab rails agent record to associate it with configuration, repository project.

A

Okay, so let's say I need to use the graphql explorer which I'll.

B

B

A

Let's copy and what these instructions said right.

A

Here create an agent path to my project, was.

A

Sample sash kubernetes agent.

A

Test an agent name. What did I say? It's going to be called first agent right.

A

Okay, okay agent 94 got it so that was successful.

A

Now, what am I supposed to do? I don't know it says, get a token.

A

Okay, so now I need to take.

A

A

And description of the token.

A

A

Let's just call it fresh agent token.

A

Okay, this was my id 94.

A

A

That okay, so I've got a secret I'll need to delete this as soon as I publish the video yeah getting blocked by my zoom window. Okay, so I got that now. I need to install the agent on the cluster okay, so I have a cluster connector through.

A

A

Go to the console.

A

Should be using my gitlab yeah yeah, it's my gitlab account. Can I have internal.

A

So let's look at clusters. I have. I have that cluster for this project called gitlab examples. So, let's just install it there.

B

A

I think I already have this created, so let me see if I can get lab agent.

B

Just delete both of.

A

These delete anything in that.

A

A

Should clean this up before I.

A

B

A

So let's go back directly to this cluster to.

A

A

When I connect to it, I'm going to run this command. That will basically use my token and do a cubesatl apply of a specific um community service description that I think I'm going to get from this docker image. So I'm going to pull a docker image, that's going to generate an agent yaml definition for my kubernetes cluster.

A

Using this token and that cast address, and then I'm going to apply that file that I got from the it's piped to the pipe from the docker run. So.

A

A

Okay, so I am connected to the gitlab example cluster. I guess I can, let's do scale um cube ctl.

A

What's your info.

A

Okay, so I'm connected to that cluster.

A

And now I just need to run this one liner command. Let's do it.

A

So the cast address we said was cast.getlab.com.

A

A

A

A

A

B

A

Let's so I think that's a permission error with my permissions in this project, see if the services were.

B

B

A

I need to do this first. Oh, I think this is under advanced installation.

A

This one line, I should have worked, let's see what.

A

A

um Just take a screenshot of what I.

A

A

A

Let's see if we keep going like this is working or not so now I need to create a manifest.

A

Okay, so it's looking at the right project, I should be able to put a manifest file in.

B

A

And just manifest.yml.

A

And have it published, let's see what happens?

A

B

A

Okay, so now I have a first.

A

A

Clusters, uh so just for the video I hit refresh, even if I'm looking at uh agent managed clusters, I still get flipped back to.

B

A

Okay, um but I have this agent record and a token for that agent so doing I was going.

B

A

Add a manifest file.

A

And this should install nginx as an example.

A

A

Okay, so don't really have any way to know what the agent is doing or did? Let's look, I don't think, there's gonna be anything here.

A

I have an agent if it were working. It would tell me last used five of the tokens last year's five minutes ago would be great if the agent I can see like that, the agent was pulling this new manifest right. Now, um let's go back to.

A

Here, refresh, okay, well, that's cool! So there is an other workload that was apparently just created.

A

All right, I don't know if I can figure out it's just it is I mean I was looking at before and now it's created. So that tells me agent did what I was supposed to do. I'm not really sure what that error did.

A

Why I encountered that error? It could be because I had the services and the namespace created previously, but I'm not exactly sure and yeah would be.

A

A

Great, if, on that agent page, you could see the agent's activities, so I could now hey here in gitlab, without having to go to my kubernetes cluster itself, that the agent had pulled the new, manifest file and performed the like applied the correct actions.

A

um Okay, let me see what else so now that I have this set up. I wonder if I could are there any simple adjustments? I understand replicas, let's change the replicas from two.

B

A

Five day engine x replicas, so here I am, I just updated my git repository with this manifest file and before told me there were only two replicas.

A

Now, let's see if that gets pulled.

A

In still, oh, no, that's five. Okay, that's cool again! It would be great to be able to see that within gitlab, but certainly manifest changes are updating. um What else could I try?

A

I guess you could think about how, if you have this process, you could have. um I wonder if you can have your agent different agents looking at uh different branches.

A

So what would be great is if I guess, if I had staging in production, that I could have my staging look at a staging um branch and then the agent for that staging cluster always pulls from that from the specific branch. That's in staging. um Let's just add a note about that.

A

Can you have different agents based on.

A

Branch, so I guess the idea would be I'd. Have this manifest file, I'd edit it in.

B

A

Target branch called.

A

Staging and change this to.

A

A

A

So yeah this is staging, it has one. I would want this to be pulled, and then I could have a merge request to.

A

Master of that branch so yeah, I could say, like okay and then rotate replicas in.

A

Master and it would be cool if, in this changes, this staging branch had its own agent. I guess like this wouldn't be a feature branch, but this would be a staging branch has its own agent. That would be pulling the.

A

Manifest into it and using the one replica, and then I would have this pull request to go to master, which would update master if merged. um You could also think about that from uh yeah. You could have like.

A

Staging you could also have dynamic environments like review apps with a similar structure, where maybe you would want to create actually like point the same one, but create a separate name space for each dynamic environment on the cluster.

A

It's kind of like um similar to how our.

A

Certificate based cluster integration works today, um so cool I'm going to stop recording fairly straightforward, that one error that I think is likely more due to the fact that I'd had um some of those resources already created on the cluster, but maybe not, and I'm gonna merge this and then shut down my cluster.

A

Let's just confirm that, after that merged agents working in the background to move that from.

A

Two from five to one: it's cool um all right, thanks.

A