Juju config for containerd custom registries doesn't propogate to k8s-worker

[playworker]

Summary

I run the juju config k8s containerd_custom_registries='[{...}]' command and an appropriate hosts.toml file is created on each k8s unit in /var/snap/k8s/common/etc/containerd/hosts.d/.../, but the same thing doesn't happen on the k8s-worker units and there doesn't appear to be an equivalent juju config ... command for the k8s-worker charm.

What Should Happen Instead?

Either the same config files should be created on the related k8s-worker units, or a similar juju config ... containerd_custom_registries command should be provided for the k8s-worker charm.

Reproduction Steps

Bootstrap a new cluster, add some workers, run the juju config k8s containerd_custom_registries='[{...}]' command

System information

inspection-report-20240822_104228.tar.gz

Can you suggest a fix?

No response

Are you interested in contributing with a fix?

No response

[neoaggelos]

Hi @playworker

You should set the same configs on the worker nodes as well.

[playworker]

Hi @playworker

You should set the same configs on the worker nodes as well.

Ah, does that mean I need to raise an issue with the Charm authors if I'm using Juju?