08:00:26 <dalees> #startmeeting magnum 08:00:26 <opendevmeet> Meeting started Tue Sep 16 08:00:26 2025 UTC and is due to finish in 60 minutes. The chair is dalees. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:26 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:26 <opendevmeet> The meeting name has been set to 'magnum' 08:00:30 <dalees> #topic Roll Call 08:00:47 <dalees> o/ hi! anyone around to chat? 08:00:56 <Guest26610> o/ Hi! 08:01:21 <hemanth> o/ 08:03:57 <dalees> jakeyip, mnasiadka: ping 08:04:02 <mnasiadka> o/ 08:06:07 <dalees> No topics in agenda, but as we're close to release there are likely reviews to discuss. 08:06:15 <dalees> #topic Reviews 08:06:25 <dalees> what do we have? 08:06:43 <hemanth> I have rebased https://review.opendev.org/c/openstack/magnum-capi-helm/+/955984/5 which should be good for re-review 08:06:58 <hemanth> good to have this landed in flamingo 08:10:06 <dalees> I will have a look, I'll need another core to review also. 08:10:16 <hemanth> ack 08:10:47 <dalees> what are the implications of merging that, and then us merging something that breaks the canonical kubernetes? how will we know, and who will be interested? 08:12:10 <hemanth> I am thinking to add an optional job with canonical kubernetes once https://review.opendev.org/c/openstack/magnum-capi-helm/+/957702 is merged 08:12:50 <dalees> I need to also consider how the driver and that change is impacted by the feature freeze. Perhaps it's different to Magnum Core. 08:13:16 <hemanth> ok 08:14:02 <dalees> jakeyip, mnasiadka: any thoughts here? 08:14:37 <mnasiadka> magnum-capi-helm does not have branches, so I don't see the requirement to land this in Flamingo 08:16:05 <hemanth> Do we have plans to make branches for flamingo or defer to next release? 08:18:25 <dalees> no plans to change at this stage 08:18:52 <hemanth> ok 08:22:04 <dalees> #topic Open Discussion 08:22:16 <dalees> any other topics? 08:22:29 <hemanth> I added https://review.opendev.org/c/openstack/magnum-capi-helm/+/960941 to support proxy 08:22:36 <hemanth> Appreciate if you can review when you have time 08:22:55 <hemanth> I havent added a spec (not sure if spec is needed since its a small change) 08:25:01 <opendevreview> Merged openstack/magnum stable/2025.2: Update .gitreview for stable/2025.2 https://review.opendev.org/c/openstack/magnum/+/960536 08:25:20 <dalees> hemanth: is `proxy` supported by the charts? 08:25:53 <hemanth> I have added support to helm chart which deploys canonical kubernetes 08:27:06 <hemanth> looks something like this for canonical k8s helm chart https://github.com/canonical/openstack-capi-k8s-helm-charts/pull/14 08:28:37 <hemanth> I havent explored with https://azimuth-cloud.github.io/capi-helm-charts since the helm charts are out of magnum-capi-helm repo 08:32:12 <dalees> Ok, thanks for the links. Could you add them to the patchset also for context? 08:32:24 <hemanth> sure, will do that 08:33:41 <dalees> we'll have to decide how we'll integrate these, branching off with features in two directions of helm charts will make things tricky. 08:36:35 <hemanth> Do you have plans to make the helm chart part of magnum-capi-helm driver in future? This is tricky since the helm charts are not part of upstream project 08:41:30 <dalees> there was an intention to regularly snapshot them into an opendev repo, and use that as a known good version. 08:41:38 <dalees> or the reference version 08:44:28 <hemanth> That will be nice .. 08:45:46 <hemanth> If we can bring up CI as well as the snapshot version of chart.. then any new feature PRs can ensure change in helm chart as well.. 08:57:46 <dalees> any other topics before we close the meeting? 09:01:13 <dalees> #endmeeting