Unable to register new Node to the existing cluster

[abhishek-ch]

One of my pod triggered a new Node in Hetzner, the node got created, loadbalancer healthcheck done but registration still didnt happen

0/2 nodes are available: 1 node(s) didn't match pod anti-affinity rules, 1 node(s) had untolerated taint {CriticalAddonsOnly: true}. preemption: 0/2 nodes are available: 1 No preemption victims found for incoming pod, 1 Preemption is not helpful for scheduling.

After 15 minutes,

Nodes added to group medium-autoscaled failed to register within 15m4.901282438s

Do I need to make any manual changes to ensure the created node gets registered properly
My config

hetzner_token: 
cluster_name: test-k8s
kubeconfig_path: "./kubeconfig"
k3s_version: v1.30.2+k3s2

networking:
  ssh:
    port: 22
    use_agent: false # set to true if your key has a passphrase
    public_key_path: "~/.ssh/test.pub"
    private_key_path: "~/.ssh/test"
  allowed_networks:
    ssh:
      - 0.0.0.0/0
    api: # this will firewall port 6443 on the nodes; it will NOT firewall the API load balancer
      - 0.0.0.0/0
  public_network:
    ipv4: true
    ipv6: true
  private_network:
    enabled : true
    subnet: 10.0.0.0/16
    existing_network_name: ""
  cni:
    enabled: true
    encryption: false
    mode: flannel #cilium

  cluster_cidr: 10.244.0.0/16 # optional: a custom IPv4/IPv6 network CIDR to use for pod IPs
  service_cidr: 10.43.0.0/16 # optional: a custom IPv4/IPv6 network CIDR to use for service IPs. Warning, if you change this, you should also change cluster_dns!
  cluster_dns: 10.43.0.10 # optional: IPv4 Cluster IP for coredns service. Needs to be an address from the service_cidr range


  manifests:
    cloud_controller_manager_manifest_url: "https://github.com/hetznercloud/hcloud-cloud-controller-manager/releases/download/v1.20.0/ccm-networks.yaml"
    csi_driver_manifest_url: "https://raw.githubusercontent.com/hetznercloud/csi-driver/v2.8.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"

datastore:
  mode: etcd # etcd (default) or external
  external_datastore_endpoint: postgres://....

schedule_workloads_on_masters: false

masters_pool:
  instance_type: cax11
  instance_count: 1
  location: nbg1

worker_node_pools:
- name: small-static
  instance_type: cax21
  instance_count: 1
  location: hel1
- name: medium-autoscaled
  instance_type: cax21
  instance_count: 0
  location: fsn1
  autoscaling:
    enabled: true
    min_instances: 0
    max_instances: 2

embedded_registry_mirror:
  enabled: true

[vitobotta]

What do you see in the autoscaler logs during the scaling event?

[abhishek-ch]

I am using v2-rc2. things are running so not very sure abt upgrading cluster. Maybe will create another replica cluster

[vitobotta]

Ah that's why. Please upgrade to the very latest version as it contains several fixes, including the autoscaling :)

[abhishek-ch]

reg instance type i am using arm based so cax21

[vitobotta]

Please use v2.0.8. The rc you were using is a release candidate and there have been many fixes since then.

[abhishek-ch]

Worked, scaling/down scaling