techno-tim / k3s-ansible

The easiest way to bootstrap a self-hosted High Availability Kubernetes cluster. A fully automated HA k3s etcd install with kube-vip, MetalLB, and more. Build. Destroy. Repeat.
https://technotim.live/posts/k3s-etcd-ansible/
Apache License 2.0
2.43k stars 1.06k forks source link

Support for openSUSE flavours #565

Open pickworth opened 2 months ago

pickworth commented 2 months ago

Hi @timothystewart6 huge fan of your playbooks, but unfortuanetly they are incomaptible with my preferred distro.

I'm opening this issue just to gather your (and others too, of course) opinion on the idea of adding this and what approach you would take. Also curious if there are any known issues or attempts done in the past. Nothing obvious stands out to me

Expected Behavior

Should work on SUSE

Why?

Given that k3s is backed by them, makes sense to me :)

Current Behavior

Variations of SUSE

Scope of Support

My opinion may be biased as I'm using Leap Micro and i'm loving it, but I'm thinking it could be a good place to start as I'm assuming it is the most finicky

Possible Solution

pickworth commented 2 months ago

Few things I wanted to add..

Cheers, Nathan

berendt commented 2 months ago

@pickworth We would like this as we are currently preparing support for openSUSE for our LCM tool. I could help with an initial review and test.

pickworth commented 2 months ago

@berendt geeat! at a high level, what does your kubes cluster look like and what flavour of openSUSE are you using?

berendt commented 2 months ago

We currently use this primarily to provide Cluster API, which is then controlled by OpenStack Magnum. We will also use it for Rook in the future. At the moment there are usually 3 node clusters on our control plane. In future, it will be added to the data plane. We currently use flannel with MetalLB, but in future we planned to use Cilium.

openSUSE Leap is currently of most interest to us. For customers, however, we will then work with SLES.