Support for openSUSE flavours

[pickworth]

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

• package management commands are different
• transactional updates are broken
• some configuration file locations need to be changed
• some calls to system scripts/binaries need to be updated
• In general, there are too many to list everything, but can vary based on the flavour of openSUSE, for example, the 4 variants below would likely require

Variations of SUSE

• Tumbleweed
  For Developers, openSUSE Contributors, Gamers and Linux/FOSS Enthusiasts
  Rolling release with the latest packages provided by the openSUSE Project.

• Leap
  For Sysadmins, Enterprise Developers, and ‘Regular’ server Users
  Regular release with the benefits of both enterprise-grade engineering and community-developed innovation.

• MicroOS
  For single purpose server applications
  Designed to host container workloads with automated administration & patching

• Leap Micro
  For edge, embedded, IoT and other deployments
  Ultra-reliable, lightweight operating system built for containerized and virtualized workloads.

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

• I'll open a PR for leap micro support

[pickworth]

Few things I wanted to add..

• Current Behaviour are purely just assumptions and typical issues i would expect to run into. definately not true, tested, certain or complete
• I'd rather not maintain a fork; Question:
  • Is this something that you would be open to merging into here if I took the time to open a PR? It would mean higher maintenance of the repo moving forward. Something to consider.

Cheers, Nathan

[berendt]

@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]

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

[berendt]

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.