search

confidential-containers / cloud-api-adaptor

Ability to create Kata pods using cloud provider APIs aka the peer-pods approach
Apache License 2.0
44 stars 71 forks source link

versions: Bump fedora base image versions #1860

Closed stevenhorsman closed 2 weeks ago

stevenhorsman commented 2 weeks ago
wainersm commented 2 weeks ago

Hi @stevenhorsman !

  • Fedora 38 has passed EoL 3 weeks ago, so we should try and bump to the next version (or possibly even 40?).

I'm glad that you noticed that this time. But I was wondering how we could automatically detect distros reaching EOL and act on. I've found this https://github.com/marketplace/actions/xeol-end-of-life-eol-scan gh action that leverages this https://github.com/marketplace/actions/xeol-end-of-life-eol-scan tool. I liked both action and tool, I believe it can help on solving our problem. Worth an issue to track that idea?

Other than that, I check that mkosi based Fedora podvm is already on 39 (great!):

src/cloud-api-adaptor/podvm-mkosi/mkosi.presets/system/mkosi.conf.d/fedora.conf 

* Once `golang-fedora:1.21.11-39` is built, this will be followed up with a bump of the builder_base we use as well,
  but do to the chance of breaking things I'll keep it separate for now.

It won't make sense to run the libvirt CI as caa binary will be still built on 38 and attempted to run on 39. right?

stevenhorsman commented 2 weeks ago

But I was wondering how we could automatically detect distros reaching EOL and act on. I've found this https://github.com/marketplace/actions/xeol-end-of-life-eol-scan gh action that leverages this https://github.com/marketplace/actions/xeol-end-of-life-eol-scan tool. I liked both action and tool, I believe it can help on solving our problem. Worth an issue to track that idea?

Definitely worth an issue to track this. Thanks for the suggestion!