GitLab Alliances, 8 Jul 2022

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Deploying the GitLab Cloud-Native Operator to Red Hat Openshift

Description

Bart Zhang - GitLab Channel SA walks through deploying the GitLab self-hosted Cloud-Native operator to Red Hat Openshift. In this video, we'll review how to install the GitLab Red Hat Certified Operator and how to access your GitLab Self-hosted instance once you've deployed to Openshift.

Learn more about our partnership with Red Hat here: https://about.gitlab.com/partners/technology-partners/redhat/

A

Hey everyone today, I'm excited to share with you how to deploy gitlab self-hosted to Red Hat openshift. My name is board Zhang I'm a channel sa with Git lab and um today I'll be demoing. How exactly you can take the gitlab operator and deploy gitlab self-hosted to Red Hat openshift.

A

So the first thing you want to do in order to install gitlab self-hosted openshift is you'll, want to check operator hub for git lab and choose whether you want to install the certified or the community edition of gitlab you'll, also notice uh in the operator Hub there's, actually a couple more available charts for gitlab Runner, so gitlab Runner is an entirely separate ancillary, CI CD agent that you can install to openshift or kubernetes clusters in order to facilitate your pipeline similar to how you would, with you know, openshift pipelines or a similar, a similar open source equivalent such as tecton for example, and so that's not the focus of today's session.

A

We're going to actually just focus on deploying git Labs uh operator to Red Hat openshift, so we'll go ahead and confirm that we've installed it. If you haven't, you can click the install button up top where it says uninstall for me since I've already installed it. So let's go ahead and dive into our installed operators in our default namespace, which is the gitlab dash system, namespace and so we'll go ahead and inspect the gitlab deployment that I've created, but before we do that, let's go ahead and create a git lab deployment.

A

And so, as you can see here, this does not work out of the box, because we'll have to make some customizations we'll have to update the domain. Now I was using the default git lab sorry. The openshift provided wildcard domain and I plan on using routes instead of the default nginx Ingress um uh that that's your English controller. That's provided out of the box, so I'll go ahead and customize.

A

My um my Helm chart or my my git lab operator chart in order to indicate that I'm going to skip the install of the nginx Ingress Fork.

A

That gitlab has specifically made uh for all kubernetes and uh openshift distributions and I'm going to go with, go ahead and use the openshift uh openshift provided Ingress with openshift routes, and so in order to do that, I'm going to go ahead and copy and paste the values from the documentation in order to, in order to specify that I'm not using the nginx Ingress and allowing the openshift uh openshift Ingress router to take over and notice that this is very important.

A

You have to insert an annotation that specifies that route termination happens at the edge, so I've already gone ahead and created a gitlab deployment using these exact values. Now, if you're going to deploy out to your own openshift cluster, make sure you're using your own Wild Card domain, which typically looks something like apps dot, openshift dot, um uh and then you know whatever subdomain you you've specified or your administrator has specified when they deployed openshift to their target environment.

A

So, let's inspect uh the gitlab deployment that I've gone ahead and created.

A

As you can see, uh it's the the gitlab operator has already deployed all the deployments the replica sets and the services, as well as the secrets that you'll need to deploy your gitlab instance out to Red Hat openshift, and so, if you, if you inspect the services, you'll notice that there is a web service default service and deployment, that service actually supports our uh our gitlab web UI for our self-hosted deployment on openshift, and you can actually drill down and see how many pods are supporting it. You can scale this.

A

You can dictate how many replicas you want of the Pod at any given moment with the deployment um it's taken a while to load, but um once it does, you'll actually be able to inspect what pods are available, and if this doesn't work, I'll go ahead and jump to um actually walking through how to access your deployment.

A

Once you spun it up, so you want to go to routes and uh you you um you'll, be able to review uh the different services that are exposed through openshift uh through openshift routes uh and, as you can see here, I've got the gitlab web service, uh which actually leads you to um be able to access your gitlab deployment.

A

um And, as you can see here, uh you can use root uh and take a secret uh for for the initial root password. In this case. I've got uh it's stored in this particular secret. I'm not going to show it. But if you want to inspect your own secret, you can hit edit secret and it will.

A

It will share the secret value that you can then go ahead and input into um uh your your gitlab web UI, login and once you're once you're in you can use this account to administrate your git lab self-hosted deployment out on the openshift and, as you can see, I'm running gitlab, 15.1.1, Enterprise, Edition um and uh it'll actually tell me what components I'm using and what version of those components that um that I'm, using as part of the help chart.

A

uh And uh if you want to onboard users, you can integrate with ldap, so you can, you can do it manually or you can integrate with your ldap provider of choice, um I'm not going to demonstrate that today, but just know that that's a great way to onboard users to your self-hosted deployment.

A

Now um the gitlab web UI is not the only thing you can access through Red Hat openshifts deployment of gitlab. You can actually also access your storage administrator GUI through mideo and similarly I found the access key and the secret key within the secrets for this gitlab Dash system namespace and I've inputted it in order to access my mideo browser. So this is all protected by access and secret keys.

A

That you'll need to extract from your git lab system secrets um and, uh as you can see here, you can actually review how much storage space is being used for each particular feature set of gitlab self-hosted uh and uh there's there's, um there's storage buckets created for each feature set um such as gitlab, backups, gitlab, large file, storage, GitHub, artifacts, or even get a lot of pages and get lab terraform State.

A

um So, as you can see here, you get a full pane of glass into how how your gitlab, uh self-hosted and since is doing in terms of storage.

A

So with that I'm going to go back to openshift and uh and and conclude the tour of git lab self-hosted deployments to openshift, um with a thank you for taking the time to listen and uh and watch um this content and hope you found it interesting hope you found it helpful, feel free to reach out with any feedback or questions. You might have I'm always happy to chat.