cli
hcloud-cloud-controller-manager
Our great sponsors
| cli | hcloud-cloud-controller-manager | |
|---|---|---|
| 4 | 8 | |
| 994 | 643 | |
| 2.1% | 2.0% | |
| 9.1 | 8.8 | |
| 7 days ago | 4 days ago | |
| Go | Go | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cli
hcloud-cloud-controller-manager
-
Bare-Metal Kubernetes, Part I: Talos on Hetzner
When it comes to load balancing, I think the hcloud-cloud-controller-manager[1] is probably your best bet, and although I haven't tested it, I'm sure it can be coerced into some kind of working configuration with the vSwitch/Cloud Network coupling, even none of cluster is actually Cloud-based.
I haven't used Sidero Omni yet, but if it's as well architected as Talos is, I'm sure it's an excellent solution. It still leaves open the question of ordering and provisioning the servers themselves. For simpler use-cases it wouldn't be too difficult to hack together a script to interact with the Hetzner Robot API to achieve this goal, but if I wanted any level of robustness, and if you'll excuse the shameless plug, I think I'd write a custom operator in Rust using my hrobot-rs[2] library :)
[1] https://github.com/hetznercloud/hcloud-cloud-controller-mana...
-
Ditching ingress-nginx for Cloudflare Tunnels
Did you actually use the Hetzner LBs or did you just send traffic to the NodePort?
- Creating an ARM server with Ansible
-
Can any Hetzner user, please explain there workflow on Hetzner?
It's not even close to major public cloud providers, but this is my setup:
* https://github.com/kube-hetzner/terraform-hcloud-kube-hetzne... (Terraform, Kubernetes bootstrap)
* Flux for CI
* nginx-ingress + Hetzner Loadbalancer (thanks to https://github.com/hetznercloud/hcloud-cloud-controller-mana...)
* Hetzner storage volumes (thanks to https://github.com/hetznercloud/csi-driver)
Kube-Hetzner supports Hetzner Cloud loadbalancers and volumes out of the box, though it also supports other components.
- Tell HN: I got 10x Hetzner storage at the same price
- Error Message: missing prefix hcloud:// even with --cloud-provider=external
-
best practice kubernetes node networking
I plan to do the same or have already implemented it. I use the Hetzner private networks with the hcloud-cloud-controller-manager https://github.com/hetznercloud/hcloud-cloud-controller-manager. This creates routes so that the nodes are also connected to each other in the private network. All kubernetes resources listen on the private network. Except for the Kubernetes API, which listens on the external IP of the master so I can use kubectl from home. The actual gateway into the cluster is controlled by a load balancer from Hetzner.
-
Unable to use hcloud-cloud-controller-manager LB as ingress controller. Health check fails
I want to use Hetzner's Load Balancer as a Nginx Ingress controller. I follow this suggestion to install Nginx Ingress via helm.
What are some alternatives?
docker-volume-hetzner - Docker Volume Plugin for accessing Hetzner Cloud Volumes
etcd - Distributed reliable key-value store for the most critical data of a distributed system [Moved to: https://github.com/etcd-io/etcd]