GitLab Incubation Engineering, 16 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Incubation Engineering Server Runtime - Weekly Demo 2022-11-16

Description

This is the weekly update for the Server Runtime SEG for the week of the 16th of Nov 2022.

This week I continued to work on the custom control plane and added the following features:

1. Deploying locally and connecting to GDK
Able to deploy the custom control plane in a disconnected local kubernetes cluster

2. UI Change - Glide Settings
Enable Glide and set the URL for your instance

3. UI Change - Open with Glide Button
Can provision an IDE from the repo, an MR or from the file / blob view

4. UI Change - Dev Environments Tab
Can view the list of developer environments, see the status and open a provisioned

Chapters
0:00 Overview
0:32 Glide Settings
1:01 Open in Glide button
1:54 Dev Environments Tab
2:43 Whats next

A

Hello, everyone welcome to another update for the server runtime site for the week of the 16th of November 2022.. So this week I've been working more on the custom control plane. Some of the changes are that now we can deploy locally in a local, disconnected kubernetes cluster and also connect to the GDK I made a few UI changes. One is that you can. uh You could turn on this feature. You can start the IDE from an MR or from the repo. You can also see your existing environments from the dev environment stack.

A

So now, in the general admin area, you can look at the Glide settings now. Glide is just stands for gitlab ID, just a working name for this I would go ahead and enable this feature, and I can also point to a URL now on production. This might be glide.gitlab.com, but for for me, since I'm running this locally I'm just going to point to localhost so now uh so this is now saved.

A

So now, if I go ahead and go to any uh repository, I could actually see the open and glide button where I would normally see web IDE um I can go ahead and click on that um on on either the repository page or I can actually go to a file and click on that on the files page or I can actually go into merge, requests to an existing merge request and also click there to start guide from that particular commit.

A

uh So I'm going to go ahead and I'm going to go ahead and actually open this repository in Glide. Now since I have an existing repository, I can open since I had an existing environment. I can go ahead and click open existing, but what I want to do in my case is create a new environment and I'm going to select VI with golang and that'll start provisioning.

A

um What I want to show you now is that we also have a Dev environments: tab where you can see existing environments. You can see the current status of the provisioning.

A

um So if I go refresh, see it's it's updating the status as it does so now um you can also open an existing environment. So if I click on the open button here, it will um excuse me if I click on the open button here, it'll go and take me to an existing environment which has already been created. uh So let's just give it a few seconds for it to provision and the provision is complete, so I can go ahead and click on open and I would go ahead and open this tab.

A

For me now so now, I have this configured. I could go to uh existing file and edit it now.

A

um So that's it for this week uh next week, I want to sort of integrate it all um and have sort of one cohesive demo. I also want to start raising the Mrs to make this happen in the gitlab side. Thank you.