Wednesday, 2023-04-26

*** travissoto is now known as travisholton05:33
jakeyiphi all, mnasiadka, dalees, strigazi, anyone wants to meet today?08:49
mnasiadkahave a conflicting meeting, but if there's anything to discuss - I can watch this window ;)08:52
jakeyipok let's see if anyone else turns up08:54
daleesHello, I'm here today.08:57
* travisholton is also here08:59
jakeyipalright let's have a short one, I need some help and advice09:00
jakeyipetherpad https://etherpad.opendev.org/p/magnum-weekly-meeting09:02
jakeyip#startmeeting magnum09:03
opendevmeetMeeting started Wed Apr 26 09:03:04 2023 UTC and is due to finish in 60 minutes.  The chair is jakeyip. Information about MeetBot at http://wiki.debian.org/MeetBot.09:03
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:03
opendevmeetThe meeting name has been set to 'magnum'09:03
jakeyip#topic Roll Call09:03
daleeso/09:03
jakeyipo/ 09:03
travisholtono/09:04
jakeyipThanks for joining the meeting 09:05
jakeyipAgenda:09:05
jakeyip#link https://etherpad.opendev.org/p/magnum-weekly-meeting09:05
jakeyip#topic Supported versions for Bobcat09:05
jakeyipwe need a decision on what we should officially support for Bobcat09:06
daleeswhen does Bobcat release? K8s 1.24 is end of life 2023-07-2809:07
daleesref: https://kubernetes.io/releases/09:07
jakeyiphttps://releases.openstack.org/ Bobcat releases in 2023-10-0409:07
jakeyipdue to the differences in containerd / podsecuritypolicy / blah blah, I feel like we should not spend any effort on backwards compatibility with k8s < v1.2509:08
jakeyipmy rationale is that 1.24 will be EOL soon, and by the time someone installs Bobcat on their infra (which may be a year or more after Bobcat releases), no one will bother with k8s < 1.2509:09
jakeyipany effort supporting EOL versions is wasted09:10
daleeswell, that's a good point. 1.24 is alive now, but doesn't need to be in Bobcat in October.09:10
daleesat Catalyst Cloud *we* aim for 3 supported k8s versions, but that'd be covered with 1.25+, and we'd not need to break the older **intentionally.**.09:11
daleesI think that's reasonable for 2023-10-04 (and 1.25 EOL's in 2023-10-28).09:11
daleesSo I'd suggest we add 1.26, 1.27 to the supported list along with 1.25 for Bobcat (I have these running locally, but not certified yet)09:12
jakeyipyeah that's the plan, it'll be easier if we decided to support k8s >= 1.25 only. the breaking change is PSP09:13
jakeyipI want to support newer versions instead of worrying about backwards compatibility09:14
jakeyipwe will have to make it super clear it is breaking change in Bobcat and operators should not upgrade if they want to still support k8s <1.2509:15
jakeyipI think we have to stray from OpenStack's deprecation workflow as it does not make sense for Magnum09:15
daleesYeah, we need to be moving forward. I do maintain a few older versions of calico in our branch with Heat template `if` statements. We could do similar but it'll bloat the HOT code to keep them long term.09:15
jakeyipwhat's the 3 supported versions now for Catalyst ?09:16
daleesI was going to say, as long as there's an overlap in versions. But Magnum doesn't have upgrade paths working, so it's blue/green rebuild anyway. Might as well jump to 1.25 if you're older ;)09:17
travisholton1.23.17, 1.24.12, 1.25.809:17
dalees1.24+ with containerd09:18
jakeyipok similar for us09:18
jakeyipwe hope to drop 1.23 soon09:18
daleescool09:19
jakeyipok, similar about FCOS, I think we will also support 1 verrsion only09:19
jakeyipI have a review up at https://review.opendev.org/c/openstack/magnum/+/88056809:20
jakeyip#agreed support k8s >=1.25 only for Bobcat09:20
daleesI think I'm okay with that, the older will likely **work** but not be supported/recommended. Theres only one current "stable" FCOS anyway09:20
jakeyipthe difference in FCOS is really a pain to work with09:20
jakeyipI say document it as well as possible so operators know what verrsion to keep to09:21
daleesYeah, anything older than current stable may have CVEs. So running older is risky09:22
daleesbut we need to keep it functional the stable stream upstream changes, especially the rebases. So documenting known good versions is useful, for those who may be running older Magnum versions09:23
jakeyipyeah good point about CVEs09:24
jakeyipso hard to get user to upgrade though :D09:24
jakeyip#agreed support only 1 version of FCOS and document it09:24
jakeyipany other comments on this topic?09:25
daleessimilar topic - how  about we document "known good" template labels? We're often incrementing calico versions and the manifests to match, in our codebase. Same would apply to other `kube-system` services09:26
dalees(such as cloud provider openstack)09:26
jakeyipyeah I plan to have another change up in docs for template labels09:27
jakeyipI have some that I test with, but it's not public and it really should09:27
jakeyipI was hoping to capture that in tests too09:27
daleesgreat. If we can't change defaults due to breaking templates, then we can define them in docs so there are some known good.09:27
jakeyipsure. please help me review to docs changes so we can get them in asap09:28
daleeswill do09:28
daleesyou'll have flannel versions, and we'll have some calico versions to share.09:28
daleesIIRC09:28
jakeyipyeah that'll be great, we can iterate since it's just docs. better something than nothing (current state)09:30
jakeyipthis one needs help too https://review.opendev.org/c/openstack/magnum/+/87409209:31
jakeyipalong the same vein I'll deprecate lots of thing09:31
daleessure will do after meeting - i missed your update to that one09:31
jakeyipany other topic?09:32
jakeyipoh I have something else09:33
jakeyip#topic backport to Antelope09:33
jakeyipwe missed the Antelope deadline to get deprecation in09:34
jakeyipalso, in related news, the first version of 2023.1 has been released, but magnum isn't working because https://review.opendev.org/c/openstack/magnum/+/880820 didn't make the cut09:36
jakeyipso since the first version isn't working, I was thinking of working on some more deprecation notice, get them merged to master and backported to antelope, then release a newer version of antelope that is working09:37
jakeyipI wonder what everyone thinks09:37
jakeyipthis will allow us to remove the code in Bobcat09:37
daleesah - we need to declare the deprecations in previous release, so we can remove them in Bobcat?09:38
jakeyipyeah09:38
daleesis that reasonable for the community, to merge them now? And which code were you thinking of?09:39
mnasiadkai think it's reasonable09:41
jakeyipit'll be something like this https://review.opendev.org/c/openstack/magnum/+/83394909:42
daleesoh, yeah.09:43
daleesthat's reasonable to backport, i feel.09:45
jakeyipI want to deprecate swarm09:45
jakeyipsince fedora atomic is eol09:45
jakeyipthat review I posted made it into antelope so we can remove fedora atomic in bobcat09:46
mnasiadkamakes a lot of sense, I guess nobody would complain if we deprecated and dropped, but since we Antelope is fresh, we can backport the deprecate notice and drop in B09:46
jakeyipbut I also want to do the same for swarm and backport to Antelope09:46
mnasiadkaregarding https://review.opendev.org/c/openstack/magnum/+/874092 - so Bobcat will not support 1.24 and earlier, makes sense - how do we go about backporting this to stable branches?09:47
mnasiadkajakeyip: from my perspective - we should end up with fedora coreos k8s driver only (and CAPI once it gets merged) - sooner the better09:47
jakeyipyes that's why I want to drop as much as possible; it'll make other reviews easier too09:48
jakeyiplike the RBAC review from Rico is handling things like bay / baymodel that we want to drop in https://review.opendev.org/c/openstack/magnum/+/80378009:48
daleesRemoving PSP usage wouldn't break older versions, only if users of these versions were using that admission controller. We can decide between backporting that to Antelope, or Antelope never supporting k8s 1.25.09:49
daleesmnasiadka: +1, I'm aligned with that driver viewpoint.09:49
jakeyipdalees: do you mean Antelope never supporting k8s <1.25 ?09:50
jakeyipinstead of never supporting 1.25 :D09:51
daleesjakeyip: if we don't backport that PSP change to Antelope, 1.25 won't work, will it? (because it'll be trying to create PSPs)09:51
jakeyipoh ok sorry from different sides, I get you now09:51
jakeyipunfortunately Antelope probably will not support 1.25 and above09:52
daleesright - i guess if we backported it, the breaking change moves back too. and we don't want to do that.09:52
jakeyipbecause our release notes says 1.24 and removal of dockershim. https://docs.openstack.org/releasenotes/magnum/2023.1.html09:53
daleesok that's cool. I think that answers mnasiadka's question - we don't backport it.09:53
jakeyipmnasiadka: is that ok?09:53
mnasiadkawell, I guess from our users perspective that's a bit problematic, I'll think of somehow checking the kubernetes version in the image and basic PSP enablement on the version we get (and push that upstream), but for now it's ok ;)09:55
jakeyipI was working on that, but it got complicated very quickly due to how tightly coupled things are09:55
mnasiadkaUnderstand, I don't know if I'll have time for such mission, but we'll see09:56
mnasiadkaAnother stupid question out of the blue - Heat is deprecating SoftwareDeployment - do we need to do anything?09:57
daleesimplement ClusterAPI? :)09:57
jakeyipI've answered that we still need it ?09:57
jakeyiplol when is CAPI coming...09:57
mnasiadkaAnd assume that unicorns and rainbows will fix everything? nice09:58
daleeshaha09:58
jakeyipk8s is supposed to fix everything09:58
mnasiadkaIt's only bringing more complexity :)09:58
jakeyipI feel conned09:58
jakeyipok we are almost at time, any other thing?09:59
mnasiadkaOk, let's see what Heat comes up with - is there any alternative in Heat we could move into?09:59
daleesNot this week, but I want to discuss CAPI for Bobcat sometime. We'll be focusing some effort on it10:00
daleesdo we need it as a goal, or can it go in if it's ready?10:00
jakeyipI am not sure, will need updated from John or the stackhpc people. 10:02
jakeyipI can see them working on it so it's not abandoned. Plus they have to present at Vancouver! :)10:03
jakeyipdalees: ping him if you want to help?10:04
daleesjakeyip: yep; travisholton and I will do.10:05
jakeyipcool, we are out of time.10:05
daleesthanks all10:06
jakeyip#endmeeting10:06
opendevmeetMeeting ended Wed Apr 26 10:06:03 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:06
opendevmeetMinutes:        https://meetings.opendev.org/meetings/magnum/2023/magnum.2023-04-26-09.03.html10:06
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/magnum/2023/magnum.2023-04-26-09.03.txt10:06
opendevmeetLog:            https://meetings.opendev.org/meetings/magnum/2023/magnum.2023-04-26-09.03.log.html10:06
jakeyipthanks everyone for coming!10:06
mnasiadkathanks for running ;-)10:07
mnasiadkaanybody going to Vancouver?10:07
jakeyipnot me but 2 from Nectar will be there10:08
* dalees wishes10:08
jakeyipAPAC feels sad10:08
jakeyiphaven't had one here for long time, hopefully next year10:11
opendevreviewJake Yip proposed openstack/magnum master: Remove PodSecurityPolicy  https://review.opendev.org/c/openstack/magnum/+/87409210:32
opendevreviewMerged openstack/magnum master: [doc] Add FCOS version in Supported versions  https://review.opendev.org/c/openstack/magnum/+/88056810:35

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!