support for Debian 12 aka bookworm

[fenio]

What would you like to be added:

Support for new Debian 12 version released yesterday.

Why is this needed:

Cause install fails due to missing packages.

Seems that in Debian 12 aka bookworm some packages are missing / changed their names.

I was able to provision k8s cluster with kubespray but I had to change two lines in roles/kubernetes/preinstall/vars/debian.yml

python-apt -> python3-apt
aufs-tools -> mergerfs

To be honest I'm not really sure if mergerfs/python3-apt were used underneath to actually provision cluster but I blindly changed it and provisioning passed.

So please treat this issue mostly as a first feedback after trying to run kubespray over Debian 12 and feature request to support it as this is currently not supported setup.

[yankay]

HI @fenio

Would you please provide a PR to support Debian 12 :-)
Thanks

[sophware]

Hi @yankay

Wouldn't the PR not be based on what @fenio did? I'm going to do the same as them as a hack, but a new file is needed. There's debian.yml and debian-11.yml. It stands to reason a new debian-12.yml is needed and that one of us has to know how to make that new file get called. I'll take a look but hope someone nudges me in the right direction.

[sophware]

I created a roles/kubernetes/preinstall/vars/debian-12.yml with the following:

---
required_pkgs:
  - python3-apt
  - gnupg
  - apt-transport-https
  - software-properties-common
  - conntrack
  - iptables
  - apparmor
  - libseccomp2
  - mergerfs

That is a copy of debian-11.yml with mergerfs added. I'll do a run-through and, unless someone can amend what that list should actually be, create a PR.

[fenio]

Don't count on me @yankay. I managed to get it working but IMHO it needs tests before something usable will be ready to be merged. And I simply have no time to do that work so my bugreport was just a sign that there is a problem.

[yankay]

Don't count on me @yankay. I managed to get it working but IMHO it needs tests before something usable will be ready to be merged. And I simply have no time to do that work so my bugreport was just a sign that there is a problem.

Thanks @fenio for the bugreport :-)

[yankay]

Hi @yankay

Wouldn't the PR not be based on what @fenio did? I'm going to do the same as them as a hack, but a new file is needed. There's debian.yml and debian-11.yml. It stands to reason a new debian-12.yml is needed and that one of us has to know how to make that new file get called. I'll take a look but hope someone nudges me in the right direction.

HI @sophware

To enable the feature of Debian 12 support , there need some steps :

1. Try to run kubespray on the Debian12 environment
2. Find the issue and fix it
3. Add CI support for the Debian 12
4. Change the readme file.

[0ekk]

Hi @yankay
Wouldn't the PR not be based on what @fenio did? I'm going to do the same as them as a hack, but a new file is needed. There's debian.yml and debian-11.yml. It stands to reason a new debian-12.yml is needed and that one of us has to know how to make that new file get called. I'll take a look but hope someone nudges me in the right direction.

HI @sophware

To enable the feature of Debian 12 support , there need some steps :

1. Try to run kubespray on the Debian12 environment
2. Find the issue and fix it
3. Add CI support for the Debian 12
4. Change the readme file.

I'll try to do this job