Hetzner VMs unavailable ("resource unavailable")

[jampy]

My situation is certainly slightly special because I regularily destroy my cluster and recreate it from scratch. I do this regularily because I'm in the middle of long-running process of learning/creating/adjusting the cluster for later production use. One of my goals is that the recreation of the cluster needs to be something very well tested and not something exceptional.

The problem I'm facing however also relates to other hetzner-k3s users using the autoscaler or simply setting up a new cluster.

What I'm talking about is that more often than not, Hetzner appears to not having enough VM ressources available to start a VM of a certain type. That's also noticable in the normal Hetzner Cloud UI, where some VMs are grayed out and can't be ordered, like right now for Nurenberg:

hetzner-k3s in such a case reports the problem like this:

[Instance my-test-cluster-master2] Creating instance my-test-cluster-master2 failed: {
  "error": {
    "message": "error during placement",
    "code": "resource_unavailable",
    "details": null
  }
}

Right after deleting my cluster I often can't re-order the same VM types again and need to wait until they become available again.

This issue seems to be common.

Do we have any other options apart from just being patient? Any ideas?

[vitobotta]

Yeah this is super annoying. I am working a lot on hetzner-k3s at the moment (we use it at the day job too) so I am creating and deleting clusters very often, and this past week I have been running into resource unavailability issues quite often unfortunately.

The only workaround I have for now is that at least for the worker nodes I specify an autoscaled node pool for each instance type so during my testing I let the autoscaler pick up whichever instances are available in any location among Falkenstein, Nuremberg, Helsinki and that works fine for the workers.

But for the master and static worker node pools there isn't much we can do other than wait for new capacity or just try another location unfortunately.

[jampy]

Good points.

The problem with using another location is that (persistent, using volumeHandle) Hetzner volumes can't be attached to servers in another location.

[vitobotta]

Ah true, I hadn't thought about that.