VMware Contour Community Meetings, 16 Jun 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Contour Community Meeting - June 16, 2020

Description

June 16, 2020

What have we been working on?
Security releases
Envoy 1.14.2 has been released with a security fix.
We will release a 1.5.1 with this upgrade.
If there are any releases shortly after Contour 1.6 is released, then we will consider releasing a 1.5.2, on a case-by-case basis. If that is you, please ask.
IngressRoute removal - IngressRoute will be completely removed in Contour 1.6.
ir2proxy is available for your conversion needs. Please log issues if you find them.
ir2proxy v1.1 was recently released with TCP Proxy support.
Removing the IngressRoute code will allow us to make updates to the general CRD handling code without needing to support two code paths.
Interest in Helm Chart, we have contributors interested already, if you are also interested, please contact us in the Slack channel or look at this issues.
Please check our roadmap: https://github.com/projectcontour/community/blob/master/ROADMAP.md
This is not set in stone, but is a rough outline. We’ll keep it updated as we can.

A

Okay, well welcome to the condo community meeting for June 16th hi there, everybody and, as always, we've got the usual code of conduct stuff. Please abide by it during this meeting. Okay, so James I think I'll I'll swap the order of these two things around.

A

Let's talk about security releases.

B

Okay, so there is a envoy, 114, I, think security patch came out the other day for HTTP to settings dos issue say we haven't done a 115 one release to upgrade there and we have a contributor who's interested in pushing that release. So they just wanted to do for us to talk and get confirmation that we do want to do that. Release before I am kind of set Tim free on that yeah.

A

I think we should absolutely do a release. um I think we pretty much should almost always do a point release where it's, where we just changed the where we do the minimum amount that we need to change to do the envoy version. Hopefully that should be zero code changes most of the time and it should just be changing the UM the olive oil virgin in the deploy in the example to follow.

B

Yeah, most cool we'll go ahead. That should wish I'll talk to Tim, we'll get on that, and we should be out by the end of the week.

C

Is this I think I saw a note, so this envoi would did you get advance disclosure for this and were you once or they just go blasted out and we're gonna define like everybody else, you know.

A

So we are, we are only we are on, the tutorial is for us and we get I.

B

Don't think I got it for this particular one, but maybe I missed, maybe I mr. Barrera I, don't recall getting an ask for them for.

A

B

Points ooh, ok,.

C

Sounds good I was just wondering who had the heads up. I mean yeah yeah. So if we're gonna release one five one soon enough, then that's fine yeah, yeah.

A

Okay, cool, that's everything, I see the other big thing I wanted to mention was um yeah I'm I'm in the process of removing all the English route code. um The idea is that ingress trail will be completely cloning 1.6, which is due out in like a week and a half also so yeah I'm just smoking through as much of that as quickly as possible. Okay,.

B

So under security really started that so hypothetically, would we do security really if those we needed to do another security release, would we do that? It's one point six point one: given that we're removing on ingress route or should we stay or should we consider doing a one five, something.

C

Yeah you're asking for the folks that don't wanna so once we ship 1.6, you know, given that we don't have a long term servicing channel or we actually don't have any service in China whatsoever. I. Think that once you actually ship one six, then we're gonna have to make a release release decision. If we're gonna patch previous versions, we may do it once maybe twice max, but we may not do it at all.

C

If we were successful of upgrading all people to 1 6 or at least not giving significant pushback from any customers, then you know here's how it's gonna play out right. Let's say one: six: ships in May, June, 25 and English odd is gone and then let's say July 4th. We get an invoice security fix and we have to ship one six one once you actually ship it and publicize it. We're gonna hear from customers.

C

Everyone says: hey are you know, gonna make this available in 151 and then we're gonna have to make that decision, and it is possible. You might do it once or twice, but we'll do it and tell them. Okay, we're doing it! This time you need to upgrade 206 because 1.5 is no longer maintained. Yep.

B

Across the across the bear across the transition boundary I'm sympathetic to help people get across that boundary, so I think doing it for a short period of time is, and.

C

And, and the advantage is after people, ask us that way, we'll know who's looking for it. That way, you can help them migrate.

C

Yeah I think that I think that's fairly fair.

B

Yeah that sounds fair to me. What do you think yeah.

A

That sounds good to me, too I'm yeah, but I think as long as we cleared it, you know we're not going to do this all the time I'll put shortly after.

B

Okay, it's on o'clock on a case-by-case basis,.

C

We won't force customers to tell us that they're doing that. That way, we know about it, we'll help them and and kind of manage it rather than just win by blindly to us is not a lot of cost, but also we want to move them over the hump right, so knowing about it allows us to have a conversation was to get interact with the community a little bit more yeah.

A

Laughing sorry, James I thought my bad I had marked this one office wished. um Yeah I was pretty much done with the girl removal. Anyway, it's gonna be gone. That's it yeah!

A

That's pretty much it for the moment. We're just pretty busy like with between doing that and yeah I've just been full-time on English revenue. Whole James. Is there anything you want to talk about that you're actually working on.

B

Not really I'm, sorry to look at for one thing that would like to put in the notes, though, is that we there's some interest in the helm. Chart I have a VMware person and their next general contributor, who you have both expressed interest in doing it. There's no there's no movement on that yet, but if people are interested, it's something that I want something that I'm interested in shepherding and helping people get landed.

B

So there's a PR is a there's, an issue with the names of people who were interested and basically we just need to keep helping those people move forward. Yeah.

C

I saw some of the going back and forth on slack, so sorry on on email, so from github. So that's great, hopefully one of those folks kind of picks this up and does it Jim say, as a corollary, any update on the off work like how how's that coming along and I'm.

B

Still exploring so I'm exploring like how I think the design should be so I'm just getting to the point where I'll propose the design, so it's kind of pre-designed working around everything. Is there.

C

A date by which you were planning to propose that or just it's coming basically, it's.

B

Coming I didn't have a date in mind, but you know this later in the week or the next week. Probably okay.

C

Sounds good and then Nick you want to talk a little bit about the roadmap that we added.

A

Yeah so I think we mentioned this last one that we've got then we've added a road map.

C

Yeah I was in the u.s. community meeting, so I had like of.

A

Course so yeah we've added a road map. It is available where Michael is showing you right now. I will link in.

A

Lincoln there so yeah, but the important parts to see yeah I'm working on part of removing English rap is actually about working on the status information. Ingress route blocks, adding more fancy stuff to status off I should appear Brookley, because currently we need to support both code paths and then the next one after that is James's um thing and yeah, and the other sort.

B

Of close in one is.

A

Ingress b1 support, then, after that we're gonna start looking at exposing more on what configuration knobs read: limiting support access, long service, wild cut path matching and the helm childís markdown is October because that's when just the maintainers were looking at it, but as James said, if we've got other contributors who are interested in doing that, then then that can come in much sooner its roadmap I guess it's probably worth saying: okay,.

B

A

No sorry continue, Nick I was gonna, say this roadmap is kind of Specht out on the assumption that we have the people who are currently working on contour and they the more resources we get the quicker we can make some of this stuff happen. If you can really want some one of these things, then yeah you can totally work on it. Just talk to us first and tell us how you want to do it and- and we can work with you to Shepherd it as James says.

C

And, and the biggest thing is that this is kind of a this- is not set in stone. This is a goal and aspiration and kind of gives folks an idea of where the project is headed and a lot of timeline for one we might make some of these investments, so someone is interested in contributing and making one of these things come earlier, where you know we'll be jumping up and down and and how enable you and more importantly, you know it kind of signals to all the outsiders.

C

You know one can expect certain functionality in contour. Some priorities could change, so there's gonna be a living document, so every month, or so my revisited and see if any of these things changed and you have to update them and obviously, as things get delivered to cross them off the list.

C

We had this, that's it on that.

C

A

James Michael is there anything else from you guys.

C

Nothing else for me we're getting one more core contributor to contour, but I, don't see him online right and now I just think him asking if he has all the contour meetings so well, maybe he'll get introduced next week, so we're adding more resources to contour and and hopefully that's gonna help us accelerate our timeline and and keep delivering value on top for our customers and users.

A

I guess when I got one one, other thirty guys anything you want to talk about.

A

No nothing for me thanks great well, I guess we should call it there thanks very much everybody, and we will see you all next week.

C

Totally thank y'all.