GitLab Create Editor Group, 23 May 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Introducing remote development workspaces beta in GitLab 16.0

Description

Workspaces are available in GitLab 16.0 for Premium and Ultimate users and deliver on-demand remote development environments to improve developer efficiency.

More information in the release post (https://about.gitlab.com/releases/2023/05/22/gitlab-16-0-released/#remote-development-workspaces-available-in-beta-for-public-projects) and in our documentation (https://docs.gitlab.com/ee/user/workspace/index.html).

A

Hi everyone,, my name is eric schurter and I'm the product manager for the ide group.

A

Here at gitlab and I'm very excited to share with you the latest feature in the remote.

A

Development category called workspaces.

A

workspaces are available in beta on gitlab.com and in self-managed instances, and they provide.

A

Ephemeral, reproducible, personal remote development environments right within gitlab.

A

I want to give you a quick primer on how to configure them and then.

A

I'll give you a demo of the feature in action..

A

Our initial iteration for workspaces is sort of a "bring. Your own infrastructure" solution.

A

So the first and most important prerequisite is that you bring a kubernetes cluster to the table.

A

This can be hosted on a cloud platform of your choice or on your own server,.

A

But you need to have a kubernetes cluster that supports the gitlab.

A

Agent for kubernetes., that's the first prerequisite. and then,. Once you have that,.

A

You install the gitlab agent, uh,, the gitlab workspaces proxy, which handles authentication,.

A

And an ingress controller, so you can communicate in and out of the container.

A

Once you have those prerequisites installed,, you can enable remote development on your agent.

A

Config file with just a couple lines of code here, in the documentation.

A

So,, the next step is to prepare a project with a devfile.

A

Now,, a devfile describes your development environment in code.

A

And it is, uh, an example here in this project has a container image.

A

And that can be hosted on the gitlab container registry or anywhere else that's accessible to you,.

A

You can set memory and cpu limits, and you can expose endpoints for you. Preview server.

A

Once you have that devfile stored in the root level of your project,.

A

You're ready and you can start creating your first workspace.

A

So I'll go here to my list of workspaces., you can see. One is.

A

Already running but I'll create a new one, here.

A

I'll select the project.

A

And the agent that I have configured. in this case, I only have one,.

A

But you can have multiple agents at the group level.

A

and then we have the ability to set a time limit for automatic termination to.

A

Preserve and use your cloud resources more efficiently. if you wanted it to shut down.

A

Automatically after an hour, or five hours, or 24 hours,, you can configure that here.

A

Now I'll create my workspace, and here it is provisioning that resource in.

A

The kubernetes cluster for me., it's installing the container image and.

A

All the and configuring all the dependencies and options that were described in the devfile.

A

Great,, now that it's done, I'm going to click the link.

A

And I've opened up the web ide here in the workspace.. We are editing directly.

A

In the workspace. we plan on supporting multiple editing experiences in the future.

A

But right now we are supporting vs code,, our web ide, in the container itself.

A

Now I'll open up the readme. you can see. This is a pretty standard,. You know, text, editor.

A

My changes are tracked in the source control, but more importantly,.

A

I have access to a fully interactive shell, terminal.

A

So in here I will do npm start. or,, sorry,, npm, install.

A

And then npm start.

A

Now you see the node server is running on port 3000, which is what I defined in the.

A

Devfile. I'll show you how to a quick way to open up that preview link here.

A

I'll paste it in here, change the port in the front of the url,.

A

And just to see the node output I'll show it to you in json.

A

So that's the header request for the node server and you can see it's running in the workspace.

A

Now what I do here, I can commit back to the repository.. I can configure.

A

Additional dependencies and I can do whatever work I want to complete my.

A

Development task. and when I'm done, I can shut down my workspace and the.

A

Resources are freed. and I'll be able to create a new one for my next task.

A

That's it for today.. I hope you enjoyed the demo and I can't wait to see what you do with our workspaces. Beta. thank you.