hcloud-cloud-controller-manager
docker-volume-hetzner
hcloud-cloud-controller-manager | docker-volume-hetzner | |
---|---|---|
8 | 5 | |
646 | 102 | |
1.4% | - | |
8.7 | 7.5 | |
5 days ago | 12 days ago | |
Go | Go | |
Apache License 2.0 | MIT License |
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.
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.
docker-volume-hetzner
-
Can any Hetzner user, please explain there workflow on Hetzner?
we use https://github.com/costela/docker-volume-hetzner which is really stable.
CSI support for Swarm is in beta as well and already merged in the Hetzner CSI driver (https://github.com/hetznercloud/csi-driver/tree/main/deploy/...). There are some rough edges atm with Docker + CSI so I would stick with docker-volume-hetzner for now for prod usage.
Disclaimer: I contributed to both repos.
- Hetzner Cloud - is Volumes reliable? With Volumes mounted as /var/lib/docker for example
-
For Swarm mode users: What features do you miss/need from Kubernetes ecosystem?
The big one which would be nice: CSI support. This is currently being worked on, though. This said the current volume plugin landscape is not that dire once you realize that the local volume driver which arguably has a confusing name can work with NFS,CIFS,etc. out of the box as long as you can use fuse mounts. Besides that, we are quite happy with our setup where we use the community volume driver for our cloud provider - https://github.com/costela/docker-volume-hetzner/
-
Ask HN: Have You Left Kubernetes?
6. Volumes: Hetzner Cloud Plugin, see https://github.com/costela/docker-volume-hetzner
Reasons that we would dabble in k8s again:
1. A lot of projects are k8s only (see OpenFaaS for example)
- I do like it
What are some alternatives?
etcd - Distributed reliable key-value store for the most critical data of a distributed system [Moved to: https://github.com/etcd-io/etcd]
plural - Deploy open source software on Kubernetes in record time. 🚀
magento2-on-kubernetes - Configuration to deploy Magento 2 in a Kubernetes cluster
awesome-hcloud - A curated list of awesome libraries, tools, and integrations for Hetzner Cloud
hetzner-lb-acmedns - A service to automatically update Letsencrypt SSL certificates on the Hetzner load-balancer using joohoi/acme-dns.
crossplane - The Cloud Native Control Plane
cluster-api-provider-hetzner - Kubernetes Cluster API Provider Hetzner provides a consistent deployment and day 2 operations of "self-managed" Kubernetes clusters on Hetzner.
nydus - Nydus - the Dragonfly image service, providing fast, secure and easy access to container images.
terraform-provider-hcloud - Terraform Hetzner Cloud provider
cli - A command-line interface for Hetzner Cloud
hetzner.hcloud - A collection to manage resources on Hetzner Cloud
docker-volume-sshfs - sshfs docker volume plugin