15:06:27 #startmeeting openstack-helm 15:06:27 Meeting started Tue Jan 5 15:06:27 2021 UTC and is due to finish in 60 minutes. The chair is gagehugo. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:06:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:06:30 The meeting name has been set to 'openstack_helm' 15:07:15 #link https://etherpad.opendev.org/p/openstack-helm-weekly-meeting agenda 15:08:06 o/ 15:08:15 \o 15:08:20 o/ 15:08:57 \o 15:09:52 \o 15:09:55 nothing on the agenda today, happy new year everyone 15:10:00 #topic open discussion 15:10:24 Ive got some for open discussion, ingress api version change discussion 15:10:25 floor is open if anyone has anything 15:10:39 ok 15:11:19 SO. In 1.16 version of kubernetes, extensions/v1beta1 was deprecated 15:11:26 for ingress 15:12:04 Im working on converting armada charts for use with airship 2, and openstack-helm-addons doesnt like seeing extensions/v1beta1. it needs updated. 15:13:04 my question for the team is should we update the ingress api to networking.k8s.io/v1beta1 which has wider support since kubernetes 1.14, or switch to networking.k8s.io/v1, which is now supported for ingress in kubernetes 1.20 15:13:58 I proposed these changes https://review.opendev.org/c/openstack/openstack-helm-infra/+/768120/ and got feedback from Tin to seek input from those here 15:15:05 I believe we decided to tide the chart version to k8s version but we never decided what k8s version goes with what chart version 15:15:47 tie* 15:16:25 So we either need to finalize that process or scrap it and make a new decision here 15:16:45 good point... I guess we need to add that to the version mapping we are creating 15:17:30 what is our gate using now? 15:17:47 extensions/v1beta1, Im not sure which kubernetes version is serving it though 15:17:52 I think it is updated to 1.18 15:18:22 If it's 1.18, then networking.k8s.io/v1beta1 ? 15:18:33 it didn't matter (or rather it still does not) at the gate b/c it is linting using helm 2 15:18:49 but these things start to alarm with helm 3 15:20:55 networking.k8s.io/v1beta1 I believe is the best choice, it will see support for quite a few more release iterations of kubernetes and gets along with helm 3 from what I can tell 15:21:38 Im fine with that 15:21:43 I just prefer to use the gate as the source of truth 15:21:52 the gate lies 15:22:00 do we need to bump the version? 15:22:21 you mean major/minor version? 15:22:36 sure 15:22:54 of kubernetes? I dont believe that is necessary. a larger effort with more potential fallout 15:22:54 we should start doing releasenotes I guess 15:22:58 I mean there were mentioning that deprecating an openstack release requires a version bump 15:23:25 but it reasons that it should be done if support for k8s < 1.14 is dropped 15:23:28 +2 on release notes... or at least some highlight on major changes 15:23:48 always supportive of better docs 15:23:56 makes my life easier as an outsider 15:24:08 I'm lost too on that release support 15:24:30 I am referring to the chart version 15:24:58 osh traditionally doesn't have release cycle - so a release note out of the blue may be confusing 15:25:22 call it whatever you want, some living docs would be appreciated 15:25:23 well we have releases now technically with these chart versions 15:26:03 So for this, I assume bumping the minor version, and starting to track via release notes these changes. We will need to get a releasenote job running as well 15:26:30 Maybe make the gate start requiring release notes for any chart change 15:28:35 Any thoughts? 15:28:46 None here 15:28:51 I can work on a releasenotes job 15:29:49 If we are in agreement that networking.k8s.io/v1beta1 is the right choice I would like to get approval from the community for https://review.opendev.org/c/openstack/openstack-helm-infra/+/768120 15:30:23 jhouser: I'm fine with that, but bump the minor version instead 15:31:43 what should that be, I thought that 0.1.5 -> 0.1.6 was minor bump 15:33:11 technically that is a patch/bug fix bump, it minor update would be 0.1.X to 0.2.X 15:33:45 s/it/a 15:34:09 done 15:35:15 Should be bumped from 0.1.5 -> 0.2.0 (not 0.2.5) 15:35:37 yes, my bad 15:35:42 my example was incorrect 15:36:09 makes sense 15:36:11 too late... time for 0.2.1? 15:36:17 it bumps every 5 min... lol 15:36:23 lol 15:36:35 done v2 15:37:25 thanks jhouser 15:37:34 Does anyone else have anything for this week? 15:41:44 Well, hope everyone has a good start to the year. Thanks everyone! 15:41:47 #endmeeting