After having used #docker_swarm for many years for my private business server, it's time to say goodbye.
-
After having used #docker_swarm for many years for my private business server, it's time to say goodbye. With a little reluctance, since it has served me really well. I have always loved Docker Swarm for its simplicity and ease of use for small projects or even small businesses.
Now I'm moving on — first idea is managed #Kubernetes using #hetznerk3s, why:
* Cloud-based in Europe.
* Really good cost-benefit ratio.Anyone else using this? Recommendations, experiences?
-
After having used #docker_swarm for many years for my private business server, it's time to say goodbye. With a little reluctance, since it has served me really well. I have always loved Docker Swarm for its simplicity and ease of use for small projects or even small businesses.
Now I'm moving on — first idea is managed #Kubernetes using #hetznerk3s, why:
* Cloud-based in Europe.
* Really good cost-benefit ratio.Anyone else using this? Recommendations, experiences?
@whyhankee
A quite robust solution.
With its choice of the MicroOS (immutable server distro from openSuSE) as a host OS and a bit of configuration efforts of system-upgrade-controller and kured to automate the host and the kubernetes upgrades you may get a cluster that keep itself healthy and actual with relatively low effort.
I'd say it's easier to maintain than a AWS EKS one. -
R relay@relay.mycrowd.ca shared this topic
-
After having used #docker_swarm for many years for my private business server, it's time to say goodbye. With a little reluctance, since it has served me really well. I have always loved Docker Swarm for its simplicity and ease of use for small projects or even small businesses.
Now I'm moving on — first idea is managed #Kubernetes using #hetznerk3s, why:
* Cloud-based in Europe.
* Really good cost-benefit ratio.Anyone else using this? Recommendations, experiences?
@whyhankee Podman Quadlets are a simple way to manage containers, if you do not want / cannot use k3s.
-
@whyhankee Podman Quadlets are a simple way to manage containers, if you do not want / cannot use k3s.
@whyhankee FYI I use both Quadlets, k3s and rke2 on my servers (different ones, of course...)
-
@whyhankee
A quite robust solution.
With its choice of the MicroOS (immutable server distro from openSuSE) as a host OS and a bit of configuration efforts of system-upgrade-controller and kured to automate the host and the kubernetes upgrades you may get a cluster that keep itself healthy and actual with relatively low effort.
I'd say it's easier to maintain than a AWS EKS one.@gemelen Thank you for your reply! Helpful as Im learning!
* Arm for control plane! Good one, already saving money!
* Node-groups, that seems not available to me as I use hetzner-k3s to deploy (not tf)
* Backup, good to note. On the todo list!
* Rancher, I believe hetzner-k3s uses that, you mean to install the UI yourself? -
After having used #docker_swarm for many years for my private business server, it's time to say goodbye. With a little reluctance, since it has served me really well. I have always loved Docker Swarm for its simplicity and ease of use for small projects or even small businesses.
Now I'm moving on — first idea is managed #Kubernetes using #hetznerk3s, why:
* Cloud-based in Europe.
* Really good cost-benefit ratio.Anyone else using this? Recommendations, experiences?
@whyhankee why the change, i'm curious.
-
After having used #docker_swarm for many years for my private business server, it's time to say goodbye. With a little reluctance, since it has served me really well. I have always loved Docker Swarm for its simplicity and ease of use for small projects or even small businesses.
Now I'm moving on — first idea is managed #Kubernetes using #hetznerk3s, why:
* Cloud-based in Europe.
* Really good cost-benefit ratio.Anyone else using this? Recommendations, experiences?
@whyhankee Made the same transition myself. I’m deploying with Hetzner-k3s then argocd, with everything deployed and managed gitops style. Three arm cax11 master nodes in three locations, traefik to balance traffic, crunchydata Postgres-operator to manage my postgresql db, so far everything fits on the three masters, much to my surprise.
Haven’t even bothered with a load balancer atm - just using round robin dns atm. A lot of bang for buck! -
@gemelen Thank you for your reply! Helpful as Im learning!
* Arm for control plane! Good one, already saving money!
* Node-groups, that seems not available to me as I use hetzner-k3s to deploy (not tf)
* Backup, good to note. On the todo list!
* Rancher, I believe hetzner-k3s uses that, you mean to install the UI yourself?- node-groups: wasn't sure about non-Terraform approach, but it's possible too, check the YAML config https://vitobotta.github.io/hetzner-k3s/Creating_a_cluster/, where you could add different pools under the 'worker_node_pools'
- if the Rancher is installed by the app, then use it as is, otherwise I'd recommend to install it afterwards (via Helm, for example)
