CRI-O support limitation

[madhukarreddy326]

What would you like to be added

Hi Kubespray team,

I'm currently exploring CRI-O as the container runtime for our Kubernetes clusters and noticed that while Kubespray supports CRI-O, there are some limitations—particularly with Helm integration and certain playbooks like scale.yml and upgrade-cluster.yml.

Could you please clarify:

• Is there an official roadmap or timeline for full CRI-O support without these limitations?
• Are there any known blockers or dependencies preventing full compatibility?
• Is community contribution welcome to help accelerate this support?

Environment details:

• Kubespray version: v2.29.0
• Kubernetes version: 1.30
• OS: RHEL
• CRI-O version: 1.30

Thanks in advance for your guidance!

Why is this needed

We see CRI-O is lightweight and also standard to use so we would like to check the roadmap to remove the limitations to use the CRI-O with kubespary

[tico88612]

/retitle CRI-O support limitation
/remove-kind feature
/kind support

[tico88612]

I think it's because there was no consensus on the standard for "experimental" before (and still isn't now).
The maintainers have been constantly updating over the years, and new maintainers (including me) also don't know whether to remove it or not.

[VannTen]

IMO the main divide between experimental or not should probably be wheter it's tested in CI.

We could add some tests for CRI-O, in particular for upgrade and scale.

(Our test matrix is not somehting very cleanly defined either 😆 )