hetzner-k3s VS rke2

This is with the new version not yet released of my tool https://github.com/vitobotta/hetzner-k3s.

It uses k3s as Kubernetes flavor and Hetzner Cloud as provider. For this test I used extremely high concurrency so the tool hung twice of the process because I was hitting the Hetzner API too hard, so I had to interrupt it again and continue.

Excluding the time it paused/hubg due to the API, I calculated around 11 minutes total for the cluster creation. This includes:

- creating all the resources (cloud instances, firewall, load balancer for the Kubernetes API)

Try my project Hetzner-K3s, it’s by far the easiest and quickest way to create and manage clusters in Hetzner cloud. https://github.com/vitobotta/hetzner-k3s

Hi all, if you already use Kubernetes in any capacity or are you interested in it, would you mind spending a few minutes voting in a quick poll and hopefully answering a few questions? I would appreciate your help a ton because it would help me make the right decision and hopefully avoid a costly waste of time.

Everything is in a Github discussion at https://github.com/vitobotta/hetzner-k3s/discussions/296. A huge thank you in advance if you can help with this!

The new release introduces more customisation options for cluster/service CIDRs, cluster DNS, updated manifests for CSI/CCM/autoscaler, and a couple of improvement for creating large clusters. Check it out at https://github.com/vitobotta/hetzner-k3s

If you are already familiar with this tool, I'd love to know how it's worked for you so far. :)

https://github.com/vitobotta/hetzner-k3s

Kubernetes on Hetzner Cloud the easiest way

There’s this cool GitHub project that helps automate a lot of the process for K3s on Hetzner: https://github.com/vitobotta/hetzner-k3s

If you are willing to leave AWS in order to save a lot of money, you have an option in https://github.com/vitobotta/hetzner-k3s

In this essay, we showed how to use Rancher rke2 to deploy a Kubernetes cluster with 6 Debian nodes with firewall enabled. We've also covered deploying Cilium as a CNI for our cluster and have it completely replace kube-proxy so as to increase speed and gain more observability via Cilium tools. This article also showed how to deploy Metallb to manage IP pools and load balance traffic for those IP pools. Throughout this guide, we assumed that we have an external load balancer that will distribute traffic to our workload and control plane nodes. For further information please visit rke2 official documents: "https://docs.rke2.io/".

In this blog post, we will demonstrate how easy and fast it is to deploy Sveltos on an RKE2 cluster with the help of ArgoCD, register two RKE2 Cluster API (CAPI) clusters and create a ClusterProfile to deploy Prometheus and Grafana Helm charts down the managed CAPI clusters.

Did something happen to the Apache 2 rancher? https://github.com/rancher/rancher/blob/v2.7.5/LICENSE RKE2 is similarly Apache 2: https://github.com/rancher/rke2/blob/v1.26.7%2Brke2r1/LICENS...

To provision all of my clusters, I use Rancher with RKE2. The primary Rancher server is hosted on a bootstrapped RKE2 cluster running on a VPS.

Golang has burned me more than once with bizarre design decisions that break things in a user hostile way.

The last one we ran into was a change in Go 1.15 where servers that presented a TLS certificate with the hostname encoded into the CN field instead of the more appropriate SAN field always fail validation.

The behavior could be disabled however that functionality was removed in 1.18 with no way to opt back into the old behavior. I understand why SAN is the right way to do it but in this case I didn’t control the server.

Developers at Google probably never have to deal with 3rd parties with shitty infrastructure but a lot of us do.

Here’s a bug in rke that’s related https://github.com/rancher/rke2/issues/775

just looking at this myself. I think k3s has more support for arm, but looking through the github repo there are a lot of bugs indicating its a mess. RKE2 seems to be their big push, they also have a github issue open that has been open for the last 2 releases that they are going to add a update path from k3s to rke2. https://github.com/rancher/rke2/issues/881

RKE (https://rancher.com/docs/rke) and RKE2 (https://docs.rke2.io/) from Rancher folks