Thanks for the report. Seems like the nested LXD machine causes problems on the localhost provider. The overlay you've posted looks like a good workaround to me.
> Without the `options/kubelet-extra-config` section, the nodes never become ready for scheduling in my experience.
Thanks for the report. Seems like the nested LXD machine causes problems on the localhost provider. The overlay you've posted looks like a good workaround to me.
> Without the `options/ kubelet- extra-config` section, the nodes never become ready for scheduling in my experience.
This is a known issue that is being tracked here: https:/ /bugs.launchpad .net/charm- kubernetes- worker/ +bug/1903566