Kubernetes SIG Node, 16 May 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: SIG Node Sidecar WG 2023-05-16

Description

Meeting notes and agenda: https://docs.google.com/document/d/1E1guvFJ5KBQIGcjCrQqFywU9_cBQHRtHvjuqcVbCXvU/edit#heading=h.m8xoiv5t6qma

GMT20230516-160441_Recording_640x360.mp4

A

B

It's being recorded.

A

um Well, it's uh for the May 16 2023.

B

Signal sidecar.

A

B

Have one item on agenda.

A

It's about resource population right after they want to talk about it.

C

uh Yes, I think this will be or your simple discussion.

C

We, we decided to always calculate the part resource with sidecar containers and there there will be a problem that there will be inconsistency in resource calculation between the scheduler after 1.28.

C

And the old cubelet like 1.27, it will just calculate the part without cycle container, so I'm not sure it is dangerous. It will make some weird problem, but maybe it could be just we can just block the scheduling of the part when the future gate is disabled.

C

A

Do you think about the problem? I mean if scheduler thinks what takes more space?

A

It's not like I mean we wouldn't get into some weird situation when what being scheduled and then not being admitted on a couplet who will have enough space.

B

Yeah the two calculations to be different, but it only occurs if you're running like this mixed mode of upgraded and enabled control, plane and older cubelet fella, the the cat party says right: you should drain your nodes, was I haven't looked at it recently. Is there language regarding like, if you're going to enable this feature flag, if enabled everywhere, because it's really only for this I've half upgraded, my cluster and I'm already starting to try to run sidecar pod scenario.

C

Yes, so my question is: do we want to make this patch because it will be eventually removed after we? We graduate this feature to ga. So do we want to make this complexity in this code?.

A

We know so I mean the difference is not does not cause any problems right. So you just get all that kind of uh extra.

C

Yes, so if there is no, there will be no real problem. I would just just not block the scheduling and leave it just as it is. Is it okay.

C

What do you think all.

A

The suggestions that we write it down in cap, so I I, have my text almost ready for this. um Our previous update, uh so I will I can include this small note there as well.

B

Yeah Auto said he he wasn't keen on having this validation, the scheduler. It's got to be removed. It seems like it's a really minor Edge case and only affects if you've done, half upgrades or half down grades.

A

Said he would review uh yesterday and he left one comment: I'll double check with him like what's going on like? Is there anything else we can help us um besides,.

A

uh I, don't have anything else, just you just need to.

B

A

C

Yes and I think we need to. We need the cap PR to be approved as well.

A

Yeah so enhancements for it to started today so uh I'll double check: okay, um okay, yeah I! Don't have anything else! I'll keep thinking. People um to review the cap or to the uspr I think we're still kind of okay, we're still early in a release but, like I, think I hope we don't get in the middle of release. But uh if we'll get there, we'll need we'll need to start putting more code like resonance props.

C

Maybe we have to prepare them now, like Readiness, PR and other start to PR should be prepared.

A

A

B

A

Want waste of work, uh ideally, we need to partner.

A

um Yeah um I I listened to kubernetes podcast from Google yesterday, and uh somebody told like I, think everybody heard about sidecar containers and um last 127 release manager said that the sidecar likely going to Beta already and then they've been discussing and I think they say that it's likely going to Alpha. So it was a mistake, so it's already in Alpha in 127, so it's I I think everybody waiting for this cap so much um everybody wants that cars like people, believe that's origin.

A

Maybe we need to show this as a proof like yeah you need to. We need to merge it, because it's already.

A

B

You I don't have anything else.

A

I will go update, I think from your side.

C

Okay, thank you.