Taint Error While create k8s Cluster, Error in coredns untolerated taint

[abhishek-ch]

I tried multiple ways to create a test cluster but every time, the installation stuck in coredns Warning

0/2 nodes are available: 2 node(s) had untolerated taint {node.cloudprovider.kubernetes.io/uninitialized: true}. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.

My Config File

hetzner_token: sss
cluster_name: test-kube
kubeconfig_path: "./kubeconfig"
k3s_version: v1.29.7+k3s1
public_ssh_key_path: "~/.ssh/****.pub"
private_ssh_key_path: "~/.ssh/*****"
use_ssh_agent: false
ssh_allowed_networks:
  - 0.0.0.0/0
api_allowed_networks:
  - 0.0.0.0/0
private_network_subnet: 10.0.0.0/16 # ensure this doesn't overlap with other networks in the same project
disable_flannel: false
schedule_workloads_on_masters: false
cloud_controller_manager_manifest_url: "https://github.com/hetznercloud/hcloud-cloud-controller-manager/releases/download/v1.19.0/ccm-networks.yaml"
csi_driver_manifest_url: "https://raw.githubusercontent.com/hetznercloud/csi-driver/v2.6.0/deploy/kubernetes/hcloud-csi.yml"
system_upgrade_controller_deployment_manifest_url: "https://github.com/rancher/system-upgrade-controller/releases/download/v0.13.4/system-upgrade-controller.yaml"
system_upgrade_controller_crd_manifest_url: "https://github.com/rancher/system-upgrade-controller/releases/download/v0.13.4/crd.yaml"
cluster_autoscaler_manifest_url: "https://raw.githubusercontent.com/kubernetes/autoscaler/master/cluster-autoscaler/cloudprovider/hetzner/examples/cluster-autoscaler-run-on-master.yaml"
masters_pool:
  instance_type: cax11
  instance_count: 1
  location: fsn1
worker_node_pools:
- name: small
  instance_type: cax11
  instance_count: 1
  location: fsn1
- name: big
  instance_type: cax21
  instance_count: 1
  location: fsn1
  autoscaling:
    enabled: true
    min_instances: 0
    max_instances: 3

Console Logs

Deploying k3s to first master test-kube-cax11-master1...
[INFO]  Using v1.29.7+k3s1 as release
[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.29.7+k3s1/sha256sum-arm64.txt
[INFO]  Downloading binary https://github.com/k3s-io/k3s/releases/download/v1.29.7+k3s1/k3s-arm64
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
[INFO]  Skipping installation of SELinux RPM
[INFO]  Creating /usr/local/bin/kubectl symlink to k3s
[INFO]  Creating /usr/local/bin/crictl symlink to k3s
[INFO]  Creating /usr/local/bin/ctr symlink to k3s
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s.service
[INFO]  systemd: Enabling k3s unit
[INFO]  systemd: Starting k3s
Waiting for the control plane to be ready...
Saving the kubeconfig file to /Users/Docs/kubeconfig...
...k3s has been deployed to first master test-kube-cax11-master1 and the control plane is up.
Deploying k3s to worker test-kube-cax11-pool-small-worker1...
[INFO]  Using v1.29.7+k3s1 as release
[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.29.7+k3s1/sha256sum-arm64.txt
[INFO]  Downloading binary https://github.com/k3s-io/k3s/releases/download/v1.29.7+k3s1/k3s-arm64
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
[INFO]  Skipping installation of SELinux RPM
[INFO]  Creating /usr/local/bin/kubectl symlink to k3s
[INFO]  Creating /usr/local/bin/crictl symlink to k3s
[INFO]  Creating /usr/local/bin/ctr symlink to k3s
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-agent-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s-agent.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s-agent.service
[INFO]  systemd: Enabling k3s-agent unit
[INFO]  systemd: Starting k3s-agent

I tried restarting, change instance type commenting drivers etc but nothing worked

So I manually removed the taints from the worker node, is this a valid solution? How can I override the worker node taints?

[vitobotta]

This is very likely to delays with cloud init. Basically sometimes it can happen that cloud init hasn't finished prepping the system yet by the time the tool attempts to set up k3s on the node, so it hangs. This was addressed in the upcoming v2 which I will release soon. In the meantime can you try the v2.rc3 which is available for download? I think I will release v2 probably next weekend if I can.

[vitobotta]

Forgot to mention that the configuration must be updated with the syntax for v2, see other discussion about this, which is pinned.

[abhishek-ch]

I will follow this https://github.com/vitobotta/hetzner-k3s/blob/v2.0.0.rc3/docs/Creating_a_cluster.md, hope the config in the tag will work

[abhishek-ch]

It worked , trying LB and others now

[vitobotta]

In the Github email notification I saw you wrote that the docs are incomplete. Did you edit it? :)

[abhishek-ch]

Well loadbalancer/certificate Manager issue, ssl is not working but its not specific to this deployment, so I removed it