Support of el9 version for AlmaLinux/RockyLinux

[mr-yaky]

RHEL9 finally was released on the previous week. It means that we will get soon also a release version of el9 for AlmaLinux and RockyLinux distros. Also el9 Beta is available during last months and it's possible to start our tests.

Any plans for adding this soon ? We are ready to help with testing this on el9.

[cristicalin]

https://github.com/kubernetes-sigs/kubespray/pull/8625 was pushed a while back to make wiregurard work on centos9-stream so I kind of assume it works already.

We would need to have CI coverage to actually call this these versions supported and I'd kind of like to get 2.19 out before we make any changes to the CI.

/cc @oomichi @floryut

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[rptaylor]

Any update now that 2.19 is out? /remove-lifecycle stale

[mr-yaky]

I tried with the latest available stable version of kubespray 2.20.0 but it doesn't work with cri-o on el9. There is no upstream support for el9 yet. Only with https://copr.fedorainfracloud.org/coprs/g/OKD/okd/

Stable Releases of Upstream github.com/containers packages (CentOS_9)                                                                                         6.8 kB/s | 1.1 kB     00:00
Errors during downloading metadata for repository 'devel_kubic_libcontainers_stable':
  - Status code: 404 for http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/CentOS_9/repodata/repomd.xml (IP: 195.135.221.134)
Error: Failed to download metadata for repo 'devel_kubic_libcontainers_stable': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

So, I think we have to put some notification about this limitation in docs.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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/test-infra repository.

[rptaylor]

Looks like there was a duplicate issue, this was covered by https://github.com/kubernetes-sigs/kubespray/pull/9212 to run CI with Rocky 9 which should provide coverage for supporting other EL9 OSes as well.