No servers available in your location
Tip
If you are facing an issue and see this error message: server location disabled (resource_unavailable, *), the process described in this page will solve it.
You may be affected by unavailability of Hetzner cloud servers, which is an increasingly common issue. This can halt upgrade and self-healing processes, as no new servers can be provisioned to replace the old nodes. As a result, you may end with clusters in a degraded state, such as having only two control planes, until there is availability again.
The only way to completely avoid this is moving to Hetzner bare metal servers. It is advised to do so at least for your control planes, following the process described here . This will also avoid getting your cluster in a degraded state, for example with only two control planes, until Hetzner capacity returns.
Note
If you are going to migrate to bare metal control planes to avoid availability issues, and are on older cluster stack versions which do not support bare metal control planes, you should do the upgrade and the migration to bare metal in one single change, to avoid triggering a rollout using cloud control planes.
You can also swap your worker nodes to bare metal servers, as described here . Bare metal servers offer increased performance, a better network stack, and more cost-efficiency for your clusters.
Headless access to Syself Autopilot
How to access the Syself Autopilot management cluster without needing to interact with a browser, useful for pipelines and remote servers.
Adding HCloud servers
Efficiently manage Hetzner HCloud servers. Choose the server types according to their individual specifications based on your requirements, such as resource-efficient ARM technology.