Kubevirt & CDI Version Upgrades

[MrBones757]

G'day,

I notice both kubevirt and cdi projects have had new releases cut that have not yet made it to the suse-edge charts.

I wanted to reach out to see if this repository accepts external contributions for upgrades like this (and if any special processes need to be followed to submit such a contribution).

I note that charts in this repository use internally built images that do not seem to be built from any public repository within the suse-edge GitHub org, potentially making a contribution like this impossible; but figured it would be worth asking incase I've missed anything obvious or my github searches failed me.

I have checked change history for these charts; and note that changes like this have historically been performed by org members / suse team. Totally understand if this is a requirement.

These charts have been very handy for my personal environments; and appreciate the effort that has gone into creating them.

Thanks :)

[dprodanov4]

Hello,

Thanks for reaching out, and glad to hear the charts have been useful to you.

In general we definitely welcome contributions to this repo. At the moment, though, we’re waiting on the process to update the underlying operators/images (SLES 15.7 and SLES 16.0 container images) before we can move the charts to the newer kubevirt releases.

For kubevirt 1.6.0 specifically (which is what we currently have available in SLES 15.7), there are a few known issues we’re tracking that we’d like to see resolved before updating:

harvester/harvester#9495
kubevirt/kubevirt#15901
kubevirt/kubevirt#15711

The current plan is to cut a new release based on 1.6.3, hopefully in January, but that timing depends on how quickly these issues are resolved and the updated images are available in our SLES 15.7/16.0 repositories.