Hi all, I've been working on changing our kubernetes package to be 'truely multi-versioned', so not only will we have two versions of kubelet packaged, but the whole control plane. This is so we can offer the containers of both control plane versions, so we'll be able to do more realistic upgrade testing without worrying that the old control plane containers get tidied up when they're obsoleted. This is looking good, but has lead to an interesting side effect. In theory Kubic will now be able to support not only the latest kubernetes version, but all upstream supported versions. At time of writing this would mean packaging not only 1.18.x and 1.17.x but also 1.16.x and 1.15.x. Given there are some conservative kubernetes users out there, I can see some finding that appealing. But I don't want to package 4 versions of kubernetes all by myself. Does anyone like this idea of extending our kubernetes packaging to all currently supported upstream versions? If so, are you willing to help keep those packages updated and tested? it shouldn't be too hard for a beginner packager once we get it started :) Regards, -- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org