cluster-api-provider-hetzner
talos
cluster-api-provider-hetzner | talos | |
---|---|---|
28 | 43 | |
509 | 5,372 | |
4.3% | 4.0% | |
9.5 | 9.7 | |
2 days ago | about 6 hours ago | |
Go | Go | |
Apache License 2.0 | Mozilla Public 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.
cluster-api-provider-hetzner
-
Bare-Metal Kubernetes, Part I: Talos on Hetzner
Hetzner Cloud is officially supported, but that means setting up VPSs in Hetzner's Cloud offering, whereas this project was intended as a more or less independent pure bare-metal cluster. I see they offer Bare Metal support as well, but I haven't dived too deep into it.
I haven't used KubeOne, but I have previously used Syself's https://github.com/syself/cluster-api-provider-hetzner which I believe works in a similar fashion. I think the approach is very interesting and plays right into the Kubernetes Operator playbook and its self-healing ambitions.
That being said, the complexity of the approach, probably in trying to span and resolve inconsistencies across such a wide landscape of providers, caused me quite a bit of grief. I eventually abandoned this approach after having some operator somewhere consistently attempt and fail to spin up a secondary control plane VPS against my wishes. After poring over loads of documentation and half a dozen CRDs in an attempt to resolve it, I threw in my hat.
Of course, Kubermatic is not Syself, and this was about a year ago, so it is entirely possible that both projects are absolutely superb solutions to the problem at this point.
-
Fly.io Postgres cluster went down for 3 days, no word from them about it
For anyone interested in Kubernetes on Hetzner, there's a really interesting CAPI provider being actively developed:
https://github.com/syself/cluster-api-provider-hetzner
- Syself: Cluster API Provider Hetzner released
- Cluster API Provider Hetzner released
-
How many of you are running kubernetes on prem?
Just a hint running ML Workloads on Hetzner is pretty cheap! You could use for managing k8s: https://github.com/syself/cluster-api-provider-hetzner
-
Syself cluster-api-provider Hetzner v1.0.0-beta.16
we (Syself) release Cluster-API Provider Hetzner v1.0.0-beta.16.
-
NEW ARM-BASED CLOUD SERVER
ah okay they come from the upstream cluster-api project. The caph project implements only the infrastructure provider part of Cluster API.
-
Has anyone set up autoscaling on hetzner?
you can easily use it with https://github.com/syself/cluster-api-provider-hetzner
- Image digest of Go 1.19.7 changed?
-
What's the most sane way to operate a K8s cluster?
I would use cluster-api-provider-hetzner from Syself.
talos
-
There are only 12 binaries in Talos Linux
Super cool. I always enjoy reading about systems that challenge, well, "ossified" assumptions. An OS not providing a shell, for example? Madness! ... or is it genius, if the OS has a specific purpose...? It's thought-provoking, if nothing else.
I'm a bit skeptical of parts. For instance, the "init" binary being less than 400 lines of golang - wow! And sure, main.go [1] is less than 400 lines and very readable. Then you squint at the list of imported packages, or look to the left at the directory list and realize main.go isn't nearly the entire init binary.
That `talosctl list` invocation [2] didn't escape my notice either. Sure, the base OS may have only a handful of binaries - how many of those traditional utilities have been stuffed into the API server? Not that I disagree with the approach! I think every company eventually replaces direct shell access with a daemon like this. It's just that "binary footprint" can get a bit funny if you have a really sophisticated API server sitting somewhere.
[1]: https://github.com/siderolabs/talos/blob/main/internal/app/m...
[2]: https://www.talos.dev/v1.6/reference/cli/#talosctl-list
-
Show HN: Workout Tracker – self-hosted, single binary web application
Where `kube.cue` sets reasonable defaults (e.g. image is /). The "cluster" runs on a mini PC in my basement, and I have a small Digital Ocean VM with a static IP acting as an ingress (networking via Tailscale). Backups to cloud storage with restic, alerting/monitoring with Prometheus/Grafana, Caddy/Tailscale for local ingress.
[1] https://www.talos.dev/
[2] https://cuelang.org/
-
Google/Gvisor: Application Kernel for Containers
Looks somewhat similar to the talos Linux project[1]
[1] https://www.talos.dev/
-
Gokrazy – Go Appliances
Talos Linux basically implements their entire userspace in Go and its similar to BottleRocketOS, because it is designed to host Kubernetes.
https://www.talos.dev/
-
Old Unix programs running on modern computers
You might be surprised to find that Talos os (linux distro for kubernetes) mostly uses Go: https://github.com/siderolabs/talos
- Talos Linux – a minimal, hardened Linux distro for running Kubernetes
-
K3s – Lightweight Kubernetes
I've been using a 3 nuc (actually Ryzen devices) k3s on SuSE MicroOS https://microos.opensuse.org/ for my homelab for a while, and I really like it. They made some really nice decisions on which parts of k8s to trim down and which Networking / LB / Ingress to use.
The option to use sqlite in place of etcd on an even lighter single node setup makes it super interesting for even lighter weight homelab container environment setups.
I even use it with Longhorn https://longhorn.io/ for shared block storage on the mini cluster.
If anyone uses it with MicroOS, just make sure you switch to kured https://kured.dev/ for the transactional-updates reboot method.
I'd love to compare it against Talos https://www.talos.dev/ but their lack of support for a persistent storage partition (only separate storage device) really hurts most small home / office usage I'd want to try.
-
Bottlerocket – Minimal, immutable Linux OS with verified boot
If you’re interested in something not AWS check out Talos https://www.talos.dev/
It’s been around longer than Bottlerocket
-
What kubernetes platforms do you use in your production environment?
Can't talk about work, but my homelab is Azure and Oracle managed k8s (AKS/OKE), with onprem Talos soon (Turing Pi 2). My Flux monorepo has the details. OKE performs noticably worse (update cycle, features, control plane performance), but it provides 4 ARM cores and 24GB RAM free so I can't complain
-
Help with Kubernetes the hard way V1.26
Talos
What are some alternatives?
kubeone - Kubermatic KubeOne automate cluster operations on all your cloud, on-prem, edge, and IoT environments.
k3sup - bootstrap K3s over SSH in < 60s 🚀
free-tier-gke - Get your very own GKE cluster for next to nothing!
microk8s - MicroK8s is a small, fast, single-package Kubernetes for datacenters and the edge.
hcloud-cloud-controller-manager - Kubernetes cloud-controller-manager for Hetzner Cloud
kubespray - Deploy a Production Ready Kubernetes Cluster
cluster-api-provider-vsphere
rke2
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
ansible-role-k3s - Ansible role for deploying k3s cluster
cluster-api-k3s - Cluster API k3s
Flatcar - Flatcar project repository for issue tracking, project documentation, etc.