GitLab Distribution Team Demos, 26 Nov 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Distribution Team Demo - Nov 26, 2020

Description

The Distribution Team demos how to run a hybrid gitlab/pages deploy. With the pages server running on a omnibus VM, and all other gitlab services running in a k8s cluster.

A

Okay, uh welcome everyone to this uh distribution theme demo, so I am going to try and implement gitlab pages with the kubernetes cluster, using the hybrid method. So in in this scenario, the pages will result in a virtual machine outside of the cluster. uh All other components will be indicated with this cluster.

A

So what I have with me is a cluster running the latest latest master of the darts report. With this configuration I had I haven't enabled pages yet I just have specified a host name and an api. I have trimmed down the other components so that only one of them on one replica of each service is running.

A

This is just to avoid the message of resource. I also have an oblivious git lab instance that I have just installed the latest nightly packaged.

A

I haven't configured it or anything I haven't run reconfiguring yet so, essentially, the plan is uh we'll be using an experimental feature of that that's available at uh under a feature flag in gitlab rails. uh This will be using uh artifacts of the pages deployment ca job. uh It will be available at an object, storage bucket and we will be asking it libraries to uh serve gitlab pages contents. The page content from this artifacts uh save, like they say, file which is available at the update storage bucket.

A

So to start with, uh let's, let's enable or let's tell gitlab rails, that we are enabling pages.

A

So yeah to uncomment this setting.

A

So yeah we need a host root root domain for where the pages will be living in so this will be namespace dot. This domain, the pages will be available here.

A

uh I have it custom domain configured to point at that virtual machine that has some neighbors gitlab installed it's running over for 480 and there's a power setting which is kinda unnecessary because we are not using any shared discord, shared nfs mouse, but uh as of now gitlab pages, expect a value for this setting uh it it's not being used, but we need to have a valid uh directory from address this value and they have enabled the artifact server, which lets us view the artifacts online in line with bitmap pages, and we we are using it object, storage.

A

So technically we! If someone needs implementing this and they want pages with equivalencies. We expect it to be a production grade environment and we recommend not to use our built-in video, but for the demo purpose. I am using the mineo connection settings, but there is one catch, so uh I have to show that, let's, let's see they get labia xtml configuration.

A

uh I will be uh shutting this instance down, so it's okay to share the secrets.

A

uh Okay, if we look at the mini of configuration for the settings we can see it uses the internal service name as the endpoint, so this gitlab mini usb is the internal service name that's available only from within the cluster.

A

But for this scenario we need it to be available from the pages, the permission, because it's asking the object service to get the artifact zip file. So we kind of need to provide a custom secret to pages configuration mimicking all of this, but replacing this endpoint with the public, one that is million dot. This domain name.

A

So if you look at my configuration, I I am specifying a custom secret with this information, so I need to essentially copy all of this.

A

A

So, instead of this one, I will be reusing. The.

A

Hostname itself, okay, so this is essentially the same internal menu service, but with a modified.

A

A

Just to verify everything has gone.

A

Incorrectly, okay, so that seems to have worked.

A

Now, let's so we are, we are first deploying to the turbulent disk cluster because there needs to be a shared secret between pages and rails. This is what pages used to use as a token for invoking the internal api. So we are asking the kubernetes cluster to create that secret and we will be injecting that secret to the omnibus gitlab vm. So, let's try and deploy this uh pages there's a host.

A

I think everything should work.

A

Okay, this might take a bit of time thanks to my internet.

A

So if, if you are using a production level instance- and you are bringing your own uh of the storage, you would have already created a secret with your objective connection details uh you, you can just reuse that setting for pages object store connection secret setting in the values file.

A

uh This is because we are using the internal menu. I had to copy and recreate the connection settings.

A

uh One more thing to note: we are running the gitlab runner in the previous mode, so the then service, if, if needed, can be ram- and I have turned down the replica icon for almost everything so that only one of them runs or we can see that in.

A

Action, let's know I'm.

A

A

A

So the next high price of this hybrid method will be an in charge, page service, which is under the box.

A

I did have some sort of getting a pages run inside the cluster after some hard after hard coding, some of the settings and uh enabling a bunch of feature flags but yeah, it seems to be working so yeah fingers closed.

A

Okay, something is happening, it's the upgrade is going.

A

A

A

Okay, we have one web service note to buy one sidekick, because chrono node seems to have started.

A

Let's make sure the pages settings have gone through.

A

Okay pages is enabled access control on the bits of the pages.

A

There is a connection setting okay should work, one thing, I'm not sure if I should have used https whether it will redirect directly, but we can see that. Okay, let me check if it has created the api key.

A

Okay, there. It.

A

A

Okay, so we have an api key created with the trail set at the current site. Now we have to inject this to the vm so yeah. I have to configure the vm all the way through.

A

So this will be you using a.

A

A

A

Okay, so we are using a pages role, so all of the services should be shut down automatically. uh We have an external url for exchanges. We are specifically web server. uh We we are making the pages ask gitlab for the domain configuration, so the domain config source just gets lapped as opposed to disk, which is the default value, and we are specifying the api secret key that we have created an equivalent site.

A

A

Let's see how that.

A

A

A

A

Okay side note: this thing shouldn't come if you're not running.

A

Okay, pager c is running correctly. It was able to connect to the gitlab api.

A

So, okay, is that being done uh so we have now the omnibus gitlab and the cluster uh all configured. uh One thing we need to do is the is to enable some experimental feature, flags that makes uh pages asks of the rails for the files and they will trace to serve them from the artifacts. They see a job artifacts, so we need to be on the task. Runner.

A

Port, so these are the two features. One is ship pages deployments and under pages serve from deployments. This first one will make gitlab automatically copy the artifact ship to gitlab pages specific directory. The second one makes it serve pages from this zip file, so we can enable those two feature flags.

A

Eventually, this will become the default settings for gitlab pages, so we don't have to manually. Do this.

A

This also might take some time because it may seem here rails environment to be brought up.

A

Okay, so those two features have been enabled: let's try and create a.

A

A

Let's, let's add a ca file for hitler.

A

A

A

A

I think it should.

A

A

It's waiting for our own report to be created.

A

Okay, we now have one.

A

Okay, the deploy job.

A

A

Which is interesting.

A

Maybe there is no.

A

A

That's weird: it's not.

A

A

Oh, I want the wrong money.

A

A

So there is a gitlab pages, there are three, but it doesn't have anything. So one thing I am going to try is change this to https and see if that does.

A

A

So hopefully, when they recreated it, they will use the new secret.

A

A

A

A

Okay, it is using the https one.

A

Rest everything seems to look correct. Let's retry the.

A

A

A

Okay, it did go.

A

A

Hey, we have an output so uh yeah. Essentially this is it uh you. You need a publicly accessible object service service. You need to enable few feature flags, and uh essentially you can get github pages working in a separate vm, but with a turbulence cluster.

A

So that's essentially what I wanted to demo and I will be documenting this in the docs charts notes, so that someone who who is keen to get pages working with cluster can do it, but we will be eventually implementing pages inside cluster itself. uh So it's as easy as just specifying a domain name.

A

uh Does anyone have any questions or any anything else? They would like me to japan.

A

Okay, in that case, I think we can wind up the meeting uh thanks everyone for coming and see you.

A