Cloud Foundry CF on K8s Forum, 9 Aug 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Cloud Foundry on Kubernetes Working Group Forum Call Recording 9th August 2023

Description

2023-08-09
Recording
Docker proposal discussion: https://docs.google.com/document/d/1vJLBL1f_ebZm7YWJ9iiNa3DHhrhTOUIyBg1DzIpyuDA/

A

Well then welcome those of you that are here.

A

If we have anything to talk about. Let's do so I, don't see anything on the document, but I do saying damn it.

B

Yeah I have this song a topic about the proposal that we have for pushing docker-ups, so it has been around for some time and it's been provided some feedback and I think that the feedback is all sort. So do you think that you can start implementing it.

A

All right, let's see.

A

They're cool I, like it.

A

um So specifically just to bring it up and uh present for people see or anything on that proposes board to like uh tackle.

B

Well, I'm not pretty sure what the process should be I mean previously. We just agreed and started working on it.

C

A

A

um I, don't think the process will change that much, but uh yeah it'll be a little more interesting working a bit more across all the time zones. I am a little ambiguity about who's working on what um but yeah.

A

This might be something we have to develop over time.

B

I think that I shared a link to the proposal in the soccer channel.

B

um The only question from.

B

But it shows just for it that there might be some name questions or something containers courses, username courses whatever, but this is not going to be the case.

C

I haven't I I, unfortunately, I haven't had a chance to really actually read through the proposal, but I was just trying to understand. Like is this, generally speaking, is this updates to the the runner the Builder like? Is it a little bit of everything.

B

Well, it's uh introducing a shortcut into the Builder console that we're instead of sporting, okay, um Kpop build. It just uses the docker image and the build status in the droplet.

B

So once you have it, there are also some Minor Details that we had to take care of like introducing the docker lifecycle type as constant in the API stuff like this, and then it just works um as we described in the document, s username spaces not really much adopted.

B

So for the first implementation we can just deny running applications that are based on images that want to run this route because in kubernetes container routes node root, which is a security consideration in cflvm. We don't have this problem because Garden supports user namespaces like lots of years ago.

B

C

B

When user namespace gets largely adopted, which probably is not going to happen soon, because if you want to enable it, you have to have a pretty recent kubernetes, something that I, don't think is available in on AWS or gcp, and then the Linux kernel that notes running has to be pretty recent, like six. Three latest Ubuntu, which is 2304, runs on six two, so yeah I don't see username space, supporting kubernetes being a thing for some time.

B

A

Yeah because it's brand new, we probably don't see it mainstream for uh at least 36 months, so um I'm just looking at the proposal right now,.

C

B

Two, you can take the time to have a look at it offline and share your thoughts. We should get it going because it's been there around for some time.

B

A

Yeah I'll go through your dad today and definitely leave any comments but looks like it's fairly fleshed out. So I don't see any blockers on that.

A

And if, as you said, if we have the contacts, um it might be worthwhile to at least take an initial pass at it.

D

Sorry I just joined um did my comment on the doc around the port. Stuff make sense, yeah, okay, cool um I, think I think we have some some ideas, I think that's something we can like build on like start with 8080 and then build on later to support more images, um but we uh about a year and a half ago we were going down that road and backtrack because it didn't help build pack apps at all, but I think I think there's still some context there. That folks have.

A

Yeah, probably last not was the contacts completely so.

B

So when implementing this focus on a propagating meaningful, meaningful errors to the users, because there are quite a lot of Docker images out there that did around different port or just run this route, we have to make it very clear to the cfcla rather than push just time, outing.

A

Yeah definitely makes sense um like I, said: I, don't see any big blockers to taking initial pass at it and seeing what we find.

A

Any other uh the concerns, thoughts.

A

All right, then, I'll I'll, like I, said I'll, give it a good read today and leave any comments. I think I'm relevant, but it looks good. So let's say anyone, that's tackling yet um go for it.

A

All right, I, don't see any other topics popping up. So unless someone has a concern, this might be a really quick meeting, but um you can give people time back and then meet up again in two weeks. Oh sorry, Eric I didn't see your note. Thank you for jumping in and writing some notes.

E

Yeah I mean I just noted that we talked about the docker proposal. Somebody else wants to link in the document. That'd be great.

A

All right, let's see, let's grab it. Thank you. Interestingly. General document in the group chat um ROM. If you do have a link later for that, um the live stream or the recording of it. Please post it on the slack Channel and.

E

I would absolutely.

A

Document um like post talking, perfect awesome, um yeah I'll link in the doctor proposal. I'll. Add it to the notes after this meeting.

A

Oh all right, everyone! Well, uh unless there are other pressing concerns, I'm gonna, let you all go for now and we'll see y'all in two weeks.

B

Thanks everyone, bye-bye thanks.