Add openSUSE Leap 16.0 support and CI coverage

[yankay]

What would you like to be added

Add openSUSE Leap 16.0 support and restore representative KubeVirt CI coverage.

This includes:

• Adding an immutable Leap 16.0 cloud image and checksum to the KubeVirt image builder.
• Adding at least one representative Leap 16.0 test case.
• Updating any OS-specific package or bootstrap logic required by Leap 16.0.
• Updating the supported-distribution and openSUSE documentation.
• Retiring obsolete Leap 15.x entries from the master branch while retaining artifacts required by supported release branches.

Why is this needed

openSUSE Leap 15.6 reached end of life on April 30, 2026, and Leap 16.0 is the current supported release:

https://en.opensuse.org/Lifetime

Previous Leap 15.6 CI coverage added through #12074 was later removed because its preinstalled Python 3.6 was incompatible with the supported Ansible version. Kubespray currently documents openSUSE support but has no active openSUSE CI coverage.

Related: #11938 and #12383

[yankay]

This requires a manually built and pushed KubeVirt image; please ping me if you are interested, and I can help prepare it.
/help

[kubernetes-prow]

@yankay:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

Details

In response to this:

This requires a manually built and pushed KubeVirt image; please ping me if you are interested, and I can help prepare it.
/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[NikKumar811]

Hi @yankay I'd like to take this up. I can work on the Leap 16.0 CI/test coverage, OS-specific changes, and documentation. I'd appreciate your help with preparing the manually built and pushed KubeVirt image. Please let me know how we can get started

[yankay]

Hi @yankay I'd like to take this up. I can work on the Leap 16.0 CI/test coverage, OS-specific changes, and documentation. I'd appreciate your help with preparing the manually built and pushed KubeVirt image. Please let me know how we can get started

HI @NikKumar811
The image has been uploaded https://quay.io/repository/kubespray/vm-opensuse-leap-16-0?tab=tags

[NikKumar811]

Hi @yankay I'd like to take this up. I can work on the Leap 16.0 CI/test coverage, OS-specific changes, and documentation. I'd appreciate your help with preparing the manually built and pushed KubeVirt image. Please let me know how we can get started

HI @NikKumar811 The image has been uploaded https://quay.io/repository/kubespray/vm-opensuse-leap-16-0?tab=tags

Hi @yankay
I've completed the Leap 16 CI/testcase and OS-specific changes on my branch. I also found the two remaining Leap 15 image definitions in test-infra/image-builder/roles/kubevirt-images/defaults/main.yml. Since your image-builder PR #13453 modifies the same file, should I remove the obsolete Leap 15 entries as part of my PR, or would you prefer to handle that in #13453?