improve support of single-node clusters
This commit is contained in:
15
README.md
15
README.md
@@ -166,6 +166,21 @@ spec:
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
<summary>single-node cluster</summary>
|
||||
|
||||
Running a development cluster on a single node, without any high-availability is possible as well.
|
||||
In this case, we don't deploy an external load-balancer, but use [k3s service load balancer](https://rancher.com/docs/k3s/latest/en/networking/#service-load-balancer) on the host itself and open up port 80 & 443 in the firewall.
|
||||
|
||||
``` terraform
|
||||
control_plane_count = 1
|
||||
allow_scheduling_on_control_plane = true
|
||||
agent_nodepools = {}
|
||||
```
|
||||
|
||||
</details>
|
||||
|
||||
## Debugging
|
||||
|
||||
First and foremost, it depends, but it's always good to have a quick look into Hetzner quickly without having to login to the UI. That is where the `hcloud` cli comes in.
|
||||
|
Reference in New Issue
Block a user