late-needle-80860
10/07/2022, 10:40 AMworker
node joins cordoned in order to different processes to complete in due time before regular workloads starts piling in on the new worker
.
Some of these processes might be/are:
• the configuration of containerd
for a private self-hosted registry
• Longhorn bootstrapping … and storage space setup … which needs to be fully up and ready before potential persistent storage needing regular workloads starts appearingcreamy-pencil-82913
10/07/2022, 5:25 PMlate-needle-80860
10/07/2022, 8:05 PMregistries.yaml
indeed. That’s injected over SSH
. Haven’t found a better way of automating that as of yet.
But, it’s injected after the node becomes ready .. but maybe we should “just” inject registries.yaml
earlier … if possible.creamy-pencil-82913
10/07/2022, 8:10 PMlate-needle-80860
10/08/2022, 7:36 AMregistries.yaml
file after K3s is up is because the way the tool we use for bootstrapping K3s
clusters injects files before K3s
is fully up .. that means that the --data-dir
that we set is not ready at file injection time - e.g. when injecting into the ./manifests
folder - I’ve been assuming that was the same for the registries.yaml
file where that needs to live ( etc/rancher/k3s/server
) if I remember the path correctly.
I’ll see if that flow is an issue for the registries.yaml
file.
The HCI integration/bootstrapping Kubernetes tool we use, if interested, is https://github.com/karmab/kcli