Hi Feilong, Thanks for the reply. My issue is that currently there is no way I can overwrite hyperkube and use a 3rd party image because once I set up container_infra_prefix': ' docker.io/rancher/', magnum tries to use this registry for all images. On Sat, Oct 24, 2020 at 10:03 PM feilong <feilong@catalyst.net.nz> wrote:

Hi Ionut,

We have already made the decision actually, we would like to support both binary and container for kubelet. Spyros has started the work with https://review.opendev.org/#/c/748141/ and we will backport it to Victoria. At this stage, if you need to use latest k8s version, the simple way is building your own hyperkube image which is not difficult. You can just copy the folder https://github.com/kubernetes/kubernetes/tree/v1.18.8/cluster/images/hyperku... to the version you want to build images and follow the process. Or, you can use the hyperkube image built by 3rd parties, e.g. rancher. Please let me know if you need more information.

On 23/10/20 8:05 pm, Ionut Biru wrote:

Hi guys,

I was hoping that in Victoria there will be a decision regarding this topic. Currently, if I use vanilla magnum, I'm stuck on 1.18.6 being the latest version, even so 1.18.10 was released.

We are kinda stuck on a version that maybe in the near future is pruned to security issues.

How do other operators are using magnum (vanilla) and keeping their kubernetes up to date?

Are operators using a forked version of https://review.opendev.org/#/c/752254/ ?

-- Ionut Biru - https://fleio.com

-- Cheers & Best regards, Feilong Wang (王飞龙) ------------------------------------------------------ Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington ------------------------------------------------------

-- Ionut Biru - https://fleio.com