[08:12:23] <hashar>	 _joe_: akosiaris: good morning, I got some patches for `docker-pkg`.  One is to fix mypy after their 0.900 release: https://gerrit.wikimedia.org/r/c/operations/docker-images/docker-pkg/+/747104
[08:12:59] <hashar>	 the second is that it breaks when one does not have a `seed_image` in the config file  and dropping wikimedia-stretch entirely as the default seed image
[08:13:27] <hashar>	 I have made it so that if one ever use `{{ seed_image }}` without the variable defined, that would raise an exception
[08:13:54] <hashar>	 that is https://gerrit.wikimedia.org/r/c/operations/docker-images/docker-pkg/+/747060
[08:15:47] <hashar>	 there is also one by piotr to set `PATH` when verifying an image since `docker` might be out of the default path https://gerrit.wikimedia.org/r/c/operations/docker-images/docker-pkg/+/692995
[08:36:33] <_joe_>	 hashar: yeah I saw them, have you seen my refactoring?
[08:36:58] <_joe_>	 I want to work on all of that as soon as we're in the deployment freeze
[08:41:22] <hashar>	 _joe_: yeah I more or less did but I must confess that the whole docker-pkg code kind of confuses me :-\
[08:41:58] <hashar>	 too many layers and I never know what an `image` is or whether to use the fully qualified image name or the relative short one ;D
[08:42:27] <hashar>	 anyway lack of a seed_image in the config file is what broke for us since 3.0.1
[09:26:05] <_joe_>	 hashar: yeah that's one of the things that should work better now
[10:54:50] <varac>	 Hi, I made a PR that adds k8s 1.22 support (https://gerrit.wikimedia.org/r/c/operations/deployment-charts/+/742909) and didn't hear back so far. Wonder who could review my PR ? More details are at https://open.greenhost.net/stackspin/stackspin/-/issues/1080. (or if it even make sense to wait for it to get merged)
[11:04:00] <_joe_>	 varac: we would need to keep compatibility with the kubernetes versions we're still using
[11:04:38] <_joe_>	 sorry I completely missed the ping on gerrit, it's been a busy couple weeks
[11:07:46] <_joe_>	 varac: you'll hear back by tomorrow, I'll ask the author of the chart to take a look as well, I'm not sure what's the best way to handle such cases
[11:08:12] <_joe_>	 (we need to have a feature flag to change the apiVersion)
[11:08:44] <_joe_>	 the simplest thing would be to add a specific key to values.yaml, but I would like to manage such things in a general-ish way
[11:09:52] <varac>	 _joe_: Ok, thanks, sounds good