Antrea Community, 3 Jul 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Antrea Community Meeting 07/03/2023

Description

Antrea Community Meeting, July 3rd 2023

A

All right good morning, good afternoon or good evening, thanks for joining the entria community meeting today is the U.S Independence Day Edition I mean at least the eve of Independence Day or for those of us who are not, the U.S is just the first meeting of July and um unfortunately, for today we don't have anything in the agenda. So no pre-booked. uh uh There is no topic to discuss. uh So it's just going to be pretty much open discussion for today.

A

So if everyone in the meeting here has any topic that they would like to bring up for conversation, uh please go ahead.

A

uh Keep waiting uh for a minute I don't want this to be like a a very short meeting. So even if you have any topic pertaining the upcoming and three year, release PRS that are deserve a little bit more review, strange issues that you are debugging that will be great to discuss those together.

B

Hi Sir, Walter I think maybe I can share the current uh release. The PRS and I think I can explain thumb here so for the API promotion and I think we need more reviews for those PRS. Okay,.

A

Yeah sure good good.

B

Yeah, okay thanks my second, let me show the screen.

B

Okay, here uh here, I added some uh I think.

A

B

Helped to add the labels, so in my PRS, so I added the left with those API review cures, so we actually have a lot of API promotion appears most of them. Actually, there is no critical change. uh We actually removed the API from alpha to better one, so we can prepare them for the two dot Arrow. As you can see, we have almost uh and we have three uh I- think there might be more and another critical uh PR should be the two which we will provide to the user, so they can uh migrate.

B

The storage of the API automatically and uh for now I think honia is working on that I think at least we better have one pure for the API migration and for this peers, I I'm, hoping that we can get more reviews, and so we can mark them in time. But one question regarding those promotions is that I suppose we should merge the ci2 first before we merge those PR or it's okay, to merge this promotion pure first and maybe maybe a Tony or Jane Jun, have some suggestions or ideas, I'm, not sure.

A

uh Okay, can we make DCI changes without causing the CIT I mean? If we do the CI changes first I believe that then the CI will be failing until we emerge this PRS right.

C

um Which? Which CI changes are required.

B

C

You, what are the CI changes which are required for those PRS.

B

The CI change uh all of these uh about uh uh say: oh sorry, you mean the CI change right is that PR is not yet uh submitted. I think Honda is working on that I'm. Just uh us trying to understand that it's okay to you know merge those promotion PR first or it has to be. The ci2 has to be ready before this PR I.

C

Believe no I'm just confused by what we need to change in in CI.

B

Oh, let me uh it's actually not about the CI, it's a tool which we plan to provide sorry about this.

C

Oh, the CLI CLI tool.

B

C

B

Yeah we do have some issues and the one issue attracted our Islands once again, this one and uh to API, duplication and so- and we also like to you, know, migrate. The storage version automatically.

C

No no I, remember it's just that. I misunderstood in the studio, I thought you were saying: CI and not CLI. Okay,.

B

A

Okay, got it: okay, yeah.

C

I think salvatory had the same confusion. There I think I think we should merge the promotion PRS first and then we can introduce it tool and I think that, as long as we include both of the chain, I mean we do both of the changes before the before the release. It's it's fine, yeah, I. Think the only important thing really is that both of those changes, API promotion and the CLI tool for upgrade they should just be available in the same release. It's it's better.

C

Probably the clipr is merged like shortly after the pro version PRS, but it makes sense to merge the promotion PRS first, because they're kind of like a dependency right, it's hard to write the tool if a new version of the API is not available.

B

B

I think some of the future games are in Alpha, since we will promote the API to better I think the feature gate should also promote you to better right. Some of them have been done by churn I think the question is: should we do them uh both in the same release, or we can do in different releases.

A

A

But also, finally, if we do it in the next release,.

B

I think a list. We need to promote the API first I guess, but we do have some situation that uh the apis in Alpha, but the the data, the official gate, is in data better. So.

A

B

The last attention already.

B

Summarizes the conclusion that we will treat those API which its future gate has been in better. Then we should treat them much better right.

A

B

Yeah, okay, yeah! That's my yeah! That's my topic here. I just like to highlight those PRS which we need more reviews, but I suppose should be no big change, and another highlight is that most of them are the only API migration and just move from one photo to another folder. So it should be no webhook.

B

We just use the default web hook. The non-strategy.

B

Yeah, okay, so I thought this is uh from my side. No other topics thanks.

A

I think that's the that's. That's the that's good to know, and the only thing that I can add in terms of PR that are needing review is that we have young uh proposed the pr for which I just linked the zoom chart for admin. Network policy support in Andrea. As we know, this is a feature that the entry commute has been working on with other uh Upstream with other community members in the Sig Network in the signature policy. Community, it's been, the specification of this API is in Alpha.

A

Status has been there now for quite some time, and this implements Andrea support for it. It's very similar to the Andrea net cluster Network policies, and you know it might make sense to review and include it also because uh we renamed this to to accommodate the admin naturopolitis. We renamed the short name for Andrea Network policies, because now there was a namespace clash because both of them were amp. So um that's the pr for review and we want to include this feature in NCR, 1.13 and we'll pull in the next community meeting.

A

We also try and get young to give us a nice team of this feature, and that is the only PR that I believe these are quite a bit of review, then, for the other PRS I have to say that uh I am not uh not I, don't know if we ever need for review or not, but if you have any PR that needs reviews, please bring it up now.

B

I think one PR ior about a perform performance, enhancement I, think we need more reviews for that. Pr, maybe Greaser and the young can help on this.

A

A

Can you please share the one okay? Yes, I got uh no.

A

Okay, thanks thanks. Yes, definitely, uh unfortunately, both Grayson and yang are not are not here. Today, I'll probably talk to them on Wednesday, and since this is an area that uh the U.S been working on, I believe that it might be helpful so checking with air for the review.

A

Okay, cool- and uh this is for avoiding the uh the packet drop when we have uh um a large flow of traffic on uh only matching a given natural flow. Is that correct.

A

Yeah I mean, let me see which.

C

Yeah it's to um it's to avoid impacting traffic when we enable logging on a policy, because the rate limiting was applying both to the that's.

A

C

Which is sent to the agent for logging and to the actual user traffic packet on its way to its destination? Yeah? Okay, so effectively, you were limited at 100 packets per second, uh which is a a bit of a bummer for uh allow uh policies.

A

Okay, yeah, that's true, that's true, and uh so the only boring comment that I have is that I'm, seeing uh a few PRS which we want to include in uh Andrea 1.13 that are not set. The entry are 1.13 Milestone, so maybe PR owners. You know if you can make sure that the Milestone is set. If you want your PR, including 113, might be a good idea to set the Milestone on your PR okay and uh with that I.

A

Don't have anything else, I, don't know if anybody in the team anybody here in this meeting as a anything else that would like to discuss Please Speak now or in two weeks time. Oh of.

B

A

B

Sorry yeah, just a one I don't I like to highlight is that we will support some Wonder. Most of our testbed has been upgraded to 1.27 the kubernetes version, so we can support the latest version, released version and I think most roborks has been done, and so, when the teams trigger the test, they will be wrong in the latest kubernetes version yeah just.

A

B

Information I like to share yeah.

A

Great news and uh I know this is joined in the meanwhile, so we can also seek his feedback on the feature. Gate question that you had still learn. If I understood correctly, we are promoting uh uh these six API groups to be one better one in 1.13, and the question is whether we should make sure that all the feature gates are updated correspondingly in this release or whether it's something that we can also do in the next release. Is that correct.

B

Yeah yeah I'm, not sure Trend, if any comments for this part, but we may discuss on the issue as well.

B

D

I generally I didn't catch up. What you were discussing.

B

Yeah I think uh I just uh show that we have six apis uh going to be promoted, and the question is that we do have the future gate right. Some of the future gates are still in alpha or we need to promote them to GA. So my previous day, I was asking that so should we do this kind of a future gate promotion in one in the same release as the API promotion, or we can do in different releases.

D

uh What exactly this API are.

B

I showed that I think we have six peers for different API promotion and for the future gate there should be corresponding future gate for different API. So.

D

Yeah, for example, the field flow, API I, think you are making a PR to to to add a beta version, but a trip flow is already a better feature, so I don't get what promotion of video gate we are talking about.

B

Yeah I think most of them is in better and and for example, we should promote them to better right.

D

Egress is already better.

B

Oh okay, as I, maybe the issue might be not might not be updated. I saw. We should do that for the future. Gates. Okay,.

D

The current PR that add new versions for these Futures, they are already in beta uh feature gate stage.

B

Okay: okay, then, which this should be fine and uh for those J uh API for J I, suppose we should they should be doming 2.0 right.

D

Actually, I think this is another topic.

D

It depends on whether this future are ready to j. I I think we didn't plan for promoting them to GA in 2.0, and the arrangement plan was just to send a signal to users that they are ready for use, but we we we didn't. Then they are not experimental, but we we didn't plan to see that they are GE ready, right, I, think we we didn't talk about promoting J in the original issue, either.

B

And we should indicate that we may promote them to Jay, but uh yeah. Maybe we can I can update the issue. I can discuss you with this offline I guess if it's not a uh discussed yet.

D

B

A

Alrighty, so it seems that we come to the end of the. We came to the end of this meeting unless you have something else that you want to discuss and therefore I will leave you about 15 seconds to propose a new topic. Starting now,.

A

And time's up with this moment of silence, uh it testifies the conclusion of our meeting, so I would like to wish a great Independence Day holidays to all the community members that are joining us from United States and from the rest of us joining from the rest of the world enjoy the rest of your day.

C

Thanks goodbye.

A

Thanks, thank you. Bye-Bye.