GitLab Developer Evangelism Team, 24 Feb 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: How to install GitLab on GKE Autopilot (Part 1)

Description

In this video, Abubakar, a Developer Evangelist at GitLab introduces GKE Autopilot and demonstrates how to install GitLab on a GKE Autopilot cluster using Helm charts.

Read the announcement blogpost to learn more about GKE Autopilot: https://cloud.google.com/blog/products/containers-kubernetes/introducing-gke-autopilot

Learn other ways GitLab works with GKE Autopilot: https://about.gitlab.com/blog/2021/02/24/gitlab-gke-autopilot/

Part 2: https://youtu.be/rCwHL3hQEWU

A

Hi, I'm alpaca siddique ango, I'm developer evangelism program manager at gitlab and in this video I'll, be introducing you to the google quantities engine autopilot and how to install gitlab on a gk autopilot cluster.

A

Now, what's the difference between gke and gk autopilot gke google cloud is introducing the gke autopilot as a managed version of gke, which will now be called gke standard in the normal gke.

A

Yes, your control plane is managed, and but you still, you are still able to specify the type of nodes you want to set up, see the nodes in your compute engine interface and do a lot of things with your node, but with auto pilots.

A

Your nodes are completely managed. You no longer have access to the nodes to probably to log in or see them in the complete engine interface. They are automatically provisioned for you as your load demands. Let's say, for example, you created a deployment where you want one c, one cpu and one gig ram for your workload and you send it to do gk autopilot three kubernetes api.

A

Now it checks your prospect to now provision the nodes that you need. This saves you cost, because you get exactly what you need to run your load and your workload is stable because you don't run the risk of under provisioning and also over provisioning, making sure your application is stable and also making sure you save money. Now.

A

The only consideration you need to take note is: you cannot run privileged parts. You cannot do anything administrative with the nodes, you won't have access to the nodes and any other limitations that are common with any other managed company is offering out there. So, let's get started first to create your uk autopilot cluster. You go to your google cloud interface and to keyboard. It is engine like you do with any normal gke standard cluster.

A

Then you click on create this time previously to just simply take you to an interface where you need to specify your name, the type of uh nodes that you want to set up and so on. But now it presents you to select whether you want to set up a standard cluster or an autopilot cluster.

A

You click on configure for autopilot. Then let me minimize this for now. Then it gives you the option explaining what an autopilot cluster is, how we specify our name- let's specify gitlab dash autopilot here, go to pilots. Oh, oh, I didn't remove the force to false name.

A

I prefer using eu west one I'm based in the netherlands, and um mostly I use europe west one now then I'll leave it as public cluster, because it's a gitlab it's. I gitlab instance that I want to install on the cluster, so I need it to be publicly accessible I'll, leave everything else. As default and click on create for my previous test, it can take roughly five minutes or less for the cluster to be created. So I'll pause the video now and return once the crosstalk is fully created.

A

I won't be doing anything there's nothing else to be done. This is how you create educate.

A

A

And we are back yeah, I think, based on my timing. It took like between six to seven minutes, because I think I started around 8 pm my time when I was at the time of recording- and it's finished around seven- eight, oh seven, which is like roughly seven minutes now.

A

Our cluster is ready. You can check the cluster less access to clusters to see what other things they create. Like. I said previously, I'm installing europe west, one no specific reason just choose europolis one, because that's the one I use most often, then the default node zones are b, d and c within that using the regular channel and all the regular normal settings you'll see with uh dqe standard. But this time you don't have access to your notes. Now you can see your storage that have been provisioned here and you can see your logs here.

A

You've got to see instead of you having to go into your cluster you're running cuba, city logs, the pod name, you can see the logs from here and also the auto scalar logs. What's what's too skill are doing in the background? What decisions is he making in provisioning? Your notes for you now, let's connect to our cluster and disconnect running cloud shell, I love using crusher. I don't have to use my time now.

A

So, let's authorize that's done. Keep ctl or I mean keep ctl gets nodes now here, gke autopilot provisions, two nodes that it uses in managing your cluster.

A

Now this add just the nodes that are going to be deployed at first and if you see from uh let me go back to the list of clusters here.

A

This is the cluster created and if I refresh we'll see that the memory consumption is still zero and total cpus are allocated is zero because you've not deployed anything yet now and if we do cube cto get pods.

A

There are no poles because we've not done any deployment yet okay. Now the next thing we'll be doing is installing gitlab. The default official way to install gitlab on kubernetes is using the home charts. Now I have a guide here already in the gitlab documentation, docs.gitlab.com chats. You can see a detailed guide of how you can install gitlab on kubernetes.

A

It installs a lot of components and it's configurable. Let's say you want to use your own external storage, external database, external object, storage.

A

You can configure all of them within your value.yaml file, it's recommended if you are going to uh if your gitlab is going to be used and you want higher availability to make sure your persistence, you persist, things that need to be persisted, are external. You can use google cloud storage, you can use cloud sql and you can use the google storage for your object. Storage. Also, now the next thing we need to prepare our apple.

A

We need to the the first thing you need to do, for example, for, uh for example, if you're, installing even on gke standard, is to prepare your cluster install your cluster. We even have a script for you to install if you're, not installing, directly from the gitlab from the google cloud interface. um So let's go. The next thing you need to do is to create a public ip. This public type is necessary for gitlab to have when deploying so that it can configure what ip address key club listening on and also a dns record.

A

Dns record for uh how github should create and to like it like we use to create certificates and how to configure all the different components on what domain name. They need to listen on now to create your id you we, we have a guide here that specifies just created as not. You would normally vote on google cloud and access it now once you've gotten your your public id, you should create um a dns, a record wildcard record wildcard a record within your dns to point.

A

You can use cloud dns on google cloud to point every request that is coming to that domain, because it will create a couple of sub domains, make sure you are creating a wildcard record pointing to the ip you've created and github 100. I've already created my public ip address. I have a public ip and I've added it as a dns record to my personal domain name now. The next thing from here once you are done, is to install the charts.

A

Now, in installing the chat like I said, you need to specify you need to tell the cloud when installing with home, that okay use this domain name use the static ip address and use this email address for the search manager issuer to provision certificates for your domain names. Now everything else we are using defaults that comes with kit lab installing github out of the box straight away. We are not doing any other customization for this video, but for your own use case, you can configure gitlab in any way that suits your organization.

A

Now, let's go back to installing.

A

Gitlab I'll be installing the club by running the home command that I've already prepared, so that it'll be easier for us to just move forward as quickly on this video. Now.

A

This is what my command looks like uh helm upgrade install the name of the application I need to install out. Oh while copying I missed some things. So let me ctrl c and.

A

Yeah missed some things while copying, so let me copy this okay, it broke in half interesting. uh This is nine paste awesome, so we are doing helm upgrade and specifying the flag install. This is name of our application. I've been installing, and this is the helm chart we'll be using gitlab from gitlab, and the name of the chat is gitlab. We are specifying that it should only timeout after 600 seconds so like to allow more time for the charge to be installed now. The next thing is to set up the domain I'm using autopilot.me.

A

This is the domain wildcard area code that I've created with my dns provider. Then then specifying the ip address. I need the lab to be configured on and the email I need such months search manager, issuer email that I need it to use and I'm also setting get the git lab. uh Kubernetes agents use for githubs to be enabled. This is a different topic. You can tell that I'll talk more about it in the next video.

A

Now, let's run this and see how it goes, it checks and says: okay, there are no releases already deployed called key cloud now. This would take you a while to set up, but let's pause the video a bit and see how it proceeds.

A

Yeah back it didn't take too much time. It was actually more shorter than I expected now. This is the installation one once it's done. This is what it looks like it tells. You gives you some couple of details for you to look uh up in terms of okay, this adding new updates that have been added to the chat. Probably since the last time you used it so you'll be aware of any changes, and it also mentions to you here that the gitlab runner is deployed without the privileged flag.

A

Like I said previously, gk autopilot does not support privileged ports. Now, let's see what are you remember the other time our nodes? We only have two nodes. Now, let's see what how many nodes we have now qct arcade nodes and I have more nodes. Yeah autopilot is provisioning models, as as the demand for resources increase. Now, let's see what how many ports we have get ports, gitlab provisions, quite a lot of pots and, as you can see here, most of them are provisioning.

A

So it will take a couple of minutes for some of them to be ready as things, for example, there are migrations to be wrong and there are a lot of other things to be done in the program before everything is ready.

A

Welcome back once again now, let's check our close start to see if gitlab is ready, keep ctrl get points and voila everything is running and everything that needs to be completed has been completed.

A

Now, as you can see, it has gone through server process and one critical part you should take note of is: there are some parts that might be failing when you are installing or some that might, for example, the rona port might be filling at first because it might have completed uh it might have been created prior to other ports like the web service.

A

The sidekick are done now and the reason why this happens is there is a job migrations job that runs before everything is done, and that depends on also another port, uh which is the gitlab migrations pod, to set up to see the database and set up the database before the website can connect it before sitekey can use it, and because the web service is what the gitlab runner accesses to setup itself, it will fail, because web service is now ready and web service is dependent on the migrations for the database to be ready.

A

So just give it a little time everything will be set up if things don't go well from the beginning, we, our documentation, has a very rich troubleshooting section where you can investigate why uh a pod is failing. Now, let's visit our link, remember the other time I mentioned that the domain I specified for gitlab is autopilot.

A

Points to the public ip address we created earlier now, then gitlab adds a subdomain gitlab.com.

A

At first, your certificate search manager might not issue your certificate early or there might be some delay. Let me confirm if it has actually provisioned. Oh, it's still invalid, but it's a demo. We can proceed for now, so we're not going to use root user. But what's your initial root password you need to access. It has been created as a secret. You need to access it now how you can do that is we've already provided you need to retrieve the secret as if it has been created to contain this particular password.

A

Now, let's use the command here I'll copy. This I'll save my save some typing time. Pastes then.

A

Now all our release is called gitlab, so everything is prepended gitlab. So, let's find what's our root. Password looks like this is the root password. You should change your root password as soon as you log in for the first time for this demo, I'll I'll, be deleting the instance by viewing very soon so. Voice sign should take us straight away to the gitlab interface voila.

A

Now nope, I'm not saving this password. So, as you can see here, you will have the latest version of gitlab install. I think, as a time of this recording is 13.9. Oh, I didn't click. Let me click yeah 13.9 ee.

A

Everything is set up, fine everything's working perfectly. It even has to run or registered oops. The runner is not registered yet once the runner is complete has completely registered. It will appear here now. The uh you can. The beautiful thing about installing uh gitlab, auto gkr on gke autopilot is as more resources are needed for you to support your developers, your users, but autopilot provisions or apps, more resources skills your cluster to be able to support.

A

Your needs so in the next video I'll be showing you how to integrate an additional cluster, an additional gke autopilot cluster to your gitlab instance. So you can deploy your applications using autodevops. See you in the next video.