Cloud Foundry CF on K8s Forum, 25 Jan 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: CF on K8s WG Forum 25th Jan 2022

Description

Our first milestone (https://github.com/cloudfoundry/cf-k8s-controllers/milestone/1)!
Eirini repositories in incubator
Presentation at CFF Governing Board Meeting Feb. 23

A

Awesome, so thank you, everyone for attending this meeting. Again, it's the uh cfn kate's working group forum, where we can discuss anything and everything related to the cloud foundry ecosystem on kubernetes.

A

There is a document that should be linked in the chat that everyone can look at and add topics to if you do not wish to directly add them to the document. Please drop your questions in the chat and I can have them for you.

A

Welcome to everyone. That's here returning or for the first time and let's just get started, kicking off the first topic on our list, which is our first milestone with a little link.

B

Yeah, so I think last time we talked about uh releasing and when that could potentially happen, uh I have created a github milestone for our first release. I've called it version 0.1 and yeah. The consensus in the team is that feature-wise we're actually happy with what we have now, but at the same time we don't want to release without having all end points uh actually uh having users using user scoped authentication.

B

So what I've done is I've added all the stories to backfill user scoped authentication to all endpoints that we have the moment to the milestone and once they're, not all stories, so the milestone looks more far ahead than it actually is because I still need to create a bunch of stories, but once those are done, then I guess we can just click the button and release, something which is exciting if you feel there is anything that belongs to the milestone, feel free to go in and add it.

B

But I feel my impression is that uh there's nothing that is that needs to be in that is not the authorization work so hopefully not too far away.

A

Yeah, it's uh pretty much the feeling around a bunch of us. However, it would always be nice to have outside perspective, so uh anyone that isn't involved in the day-to-day uh that is at this meeting or not at this meeting, and you can tell them about it that has particular feature sets that they think are extremely important to them. Then have them make some noise, so we can make sure to include them.

B

I mean, I think, if having cf push working with the authorization actually being used, is uh I think, it's more than enough for a first release. uh We do have some endpoints that are maybe not directly hit by cf push.

B

So we, our scope at the moment, is our surface, is actually a bit a bit larger than cf push, and then we want to cover all of it with before, releasing so we're going to release something that is a bit more than just authenticated. Cf push, but I think it's a pretty decent scope for a first release. People can install it push see that it works. That would it would not be bad at all.

A

Absolutely yeah and uh big thanks to everyone, that's been working on all of it. It's a pretty monumental task to cover all the different parts of it. The surface area is quite large.

B

Yeah, luckily, uh we I think we're going through it relatively swiftly. So like it's lots of tiny tasks, but they are they all more or less. Look the same now that we've nailed like the design, so hopefully it's not gonna, take too long to be to be done with with all of them.

A

Cool any uh comments or thoughts from anyone else before we keep moving.

A

Alrighty, the next topic is irene repositories in incubator, yeah, I've been doing some uh housekeeping in the cloud. Foundry incubator, uh github.

B

A

um The toc decided that um we would just kind of sunset that org and move all active repositories into the cloud, foundry org and then archive those that are no longer being worked on and there's a there's, six irene repositories there, um I'm wondering uh which of those uh should be moved over and brought under the purview of the cf1k's working group. um There's irini iranian release, irony ci, irony, staging ird controller and irene helm release so um talk about that with with someone after.

C

The meeting or, if you want to address all those right now, we could.

B

Yeah it's funny because there is definitely like some of those repositories are effectively abandoned, like they were part of uh cfo cates, so they were part of the old flow with a cloud controller and if so, they can probably follow the same.

B

Like life cycle like if cfocate is being marked as deprecated or I don't know, what's happening to it, then the thing should happen to the arena release the controller is the is, uh is a dependency of the of cfo case of the current product. So we want to keep that- and I guess this, the ci with it, although we should maybe think about, I don't know either merging the two code bases like they used to be maintained by two different teams, but it's not the case anymore.

B

So maybe they don't make sense as standalone things anymore. I don't know but yeah. I guess we can just sit down and go through them, one by one and decide what to do with them.

A

Yeah the uh ones that are used in cf for kids, we should probably keep around just for any security updates if we need them um and then, as mentioned irony controller, is currently used in our efforts for cf long gates. um One extension off of this topic is that we are looking into making it flexible enough to have various different orchestrators so that you can have irene or you can have something else. Direct deployments or staple sets, or something like cartographer or whatever.

A

So, while we should still move those over to cloud foundry, um it might not be a hard requirement in the future for it. So it should be interesting on that side, but yeah we can all discuss between a few of us to figure out which ones need to be merged which ones need to be moved over and which ones can be archived great yeah. Thank you just reach out to me whenever you have a kind of definitive answer for for those six thanks cool sounds good. Thank you all right.

A

I see the list in chat awesome all right, uh so we have another topic from chris as well, which is a presentation at cff governing board meeting february 23rd yeah, that's going to be the first cloud foundry governing board meeting um of the year um coming up in just about a month- um and I was I was thinking- it'd- be great to get a presentation of some kind on um on wherever the the cf1 case product is at um regardless.

A

You know if, if there's been a initial release by then or not, you know just kind of a update on where things are at what that release is going to look like or what it does look like.

A

It could be one or two people, um but some representatives, maybe the tech needs, are or or whoever would like to just give a you know, 15 minute or longer presentation on this yeah. It sounds good, I think, between the group of us. We should be able to field some people that either want to volunteer or feel that it would be a good idea, so we can discuss it in slack and get back to you on who will be on the list.

A

That'd be great thanks, yeah, let me just make sure you said about two representatives.

A

uh Yeah or it could be, one could be two I wouldn't imagine more than that would make sense, and uh let me just give you the time of that meeting too. Just so you know um that is going to be.

A

uh 11 a.m: uh eastern so 8 a.m, on the on the west coast, so a little earlier than this meeting, but not very far, yeah, not not that much.

B

A

It works, works for probably either side of the pond and possibly other parts of the planet that.

B

I don't recall.

A

The time zones for yeah- it's not it's, not bad for a west coast or europe, so cool awesome. Well, we will definitely do that and get something prepared great thanks, so much yeah absolutely uh so that looks like the end of our quick topic list.

A

For this week, I can open the floor to any off the cuff questions that people want to ask- or I can you know, answer concerns or just elaborate on some of the work about orchestration that we're doing that we're exploring, although that will be forthcoming later on, when we actually decide to try to abstractly implement some of that stuff. So it might be worth just giving time back to people.

A

Thoughts thumbs up thumbs down uh what what's.

D

Up yeah any updates about the public roadmap that we chatted about. Last time we were together.

B

A

B

Yeah I mentioned that we have a milestone now in place uh once I have all the stories that we think are needed like that, we want to be in uh zero, one which would be on in the first release.

B

Then you kind of have an idea of the progress like how far we are into releasing and yeah once once all the stories are done, then, apparently, there's no. We there's no other major blockers, so we should be able to release something.

B

I wonder if we have some documentation blockers or something like that like what does it mean for us to be ready to release like do? uh Do we feel confident that people will be able to install this thing easily or do we need to do some extra work on that side, um like distribution, work, basically or ci? Like that, we happy with the ci. Do we want to automate the process of the ship of releasing before the first release?

B

But are we happy to release something and then figure that out later, I guess these things will have to figure out, but whatever we decide we'll put everything into the github milestone and you'll? Be able to see the progress, so we don't have dates like I don't think it makes sense to come up with dates. But you see you see how we're covering the scope.

E

Right, I mean one of the other things that um I'm also looking to extract from sorry about the kid noises I tried to kick them out of the room, but they came right back. So one of the other uh things that I'm trying to extract from this public roadmap is a sense of you know.

E

What are the big issues that we are tackling now, I'm very happy the way you've carved out this v 0.1 milestone, because it gives a clear picture about uh the earth issues being at the forefront of it, and you know you want to limit this to a certain scope and I think that's a very crisp and valuable summary of here's. What we are targeting for, like the first cut as a milestone.

E

So um if it is possible- and you know I I could be kind of greedy here- but if it's possible to sort of create a similar pattern in terms of you know, these are sort of the big issues or these are sort of the big groups in terms of features that we are targeting for every subsequent release.

E

It gives us at the foundation an opportunity to you know, write something about you know what's coming or uh speak about, you know what's coming up in uh different forums, so that's really the perspective that I'm uh asking about this one, not um in order to sort of push folks or to put treasure but more in terms of preparing the market and the audience and our community.

E

For you know, this is what you have coming up, and you know if there's something that you'd like to prioritize speak now versus uh stuff, like that.

B

Yeah I mean we should have probably done it sooner and we should get into the habit of doing it in the future. Like every every release, we just create a milestone like automatically, and uh so that makes it visible to everyone like what's missing and how far we are, etc.

A

Yep, I think that all makes sense. um I think we have some thoughts going forward as to what will be in the next milestones, but we should really sort of collate that and put up ahead of any release that goes off of whichever milestone we decided to stage our initial release. Off of um so that's that's good feedback for the community and for the foundation to be projecting uh forward as to what the feature set will be so that we can get that messaging out. So thank you for bringing that up.

A

All right well, then, any other thoughts before we break for the next two weeks and hopefully run down a bunch of the rest of the stuff for that 0.1 milestone.

A

All right cool well, once again, thank you. Everyone for coming- everyone that's been here before, and everyone that's come for. The first time uh feel free to drop topics uh in the slack channel. If you wish to have them in ahead of time or you might now have the working group forum link to the notes, so you can try adding them there and we look forward to seeing you all again in about two weeks thanks all thanks. Bye.