GitLab Configure Stage, 18 Oct 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab Kubernetes Agent: Register and install into your cluster

Description

No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).

A

Hello to this short demo, video of how to register and install the commands agent into your cluster. My name is victor knight and I am the product manager here of git lab.

A

I made a few prerequisites already to make this a short video. First of all, I have a project. I will speak about that a little bit later and I have a cluster set up and I'm connected to that cluster from my local terminal, because I will have to run a few comments so make sure that you are connected as well. I will open another terminal as well just to make sure that we are clean here here.

A

You can see, there's not no namespace, that relates to anything around the agent, but will this will soon change so a few words about this project. First, as you can see, there is no gitlab crm file. There is just a dot back file, but no yam will find this project at all. Second, there is a file under dot.

A

Gitlab, slash agent slash a directory, especially that file is this configurable that configures the agent and in this case it configures it to deploy an example yaml from within this project itself, and we are going to deploy this yaml that creates a namespace and a deployment that deploys nginx in two replicas.

A

So how do you do that? You should head to the infrastructure, menu kubernetes clusters and select the gitlab agent manage clusters tab.

A

Where, once you want to integrate with the agent you can select, the agent configuration that's not registered yet, and the next step you will get the agent token. This token should never be shared publicly.

A

So I will remove this token once the video is over, as we use this token to authenticate with gitlab using the agent below the token, you can see a single one-liner installation method if you want to get started quickly, I'm going to use that now, but if you need a more elaborate installation, we have it documented in our documentation again linked on this one, but do not forget to copy the token in that case, because this is the only time when you will see that token.

A

So, let's head over to our terminal and create a cluster, a namespace first for the agent next, we can use oops.

A

Once will be enough, so we can use the okay. Let's try to.

A

Make it this way.

A

Yep, as you can see, we used namespace that we just created, and we have to provide a few other arguments as well, like the agent version, the address for the kubernetes agent server that lives besides gitlab in this case.com and the token itself, you can use a different version, of course, and we recommend you choose different version. If you run in production.

A

A

Resources are created. I already had a few things done in this cluster, but not this one. So if you go there, we can see the name space that was created by us manually and within that runs the agent.

A

On the other hand, we can see as well the other name space that was created by the agent and within that we can see two ingenious deployments thanks for watching this quick video and give a try to the agent bye.