search

rancher / elemental-operator

The Elemental operator is responsible for managing the OS versions and maintaining a machine inventory to assist with edge or baremetal installations.
Apache License 2.0
40 stars 17 forks source link

Integrate a development channel in charts #768

Closed davidcassany closed 2 months ago

davidcassany commented 2 months ago

This is a PoC to add an unstable channel for helm builds happening at isv:Rancher:Elemental projects in OBS.

davidcassany commented 2 months ago

@fgiudici @anmazzotti this is what I had in mind for setting a development channel only for projects under isv:Rancher:Elemental. So it could be a separate OBS package that is never submitted to IBS.

anmazzotti commented 2 months ago

I like this. I think you can simply add your OBS Dockerfile and .json to the elemental-channels project, this could be the Dockerfile.unstable flavor.

The only thing I miss is when this image is refreshed. Can we for example trigger the elemental-channel service after build-baremetal-iso-image succeeds?

Otherwise the elemental-channels Github refresh action runs nightly, but for a development image I'd really love to always have the latest latest.

davidcassany commented 2 months ago

I like this. I think you can simply add your OBS Dockerfile and .json to the elemental-channels project, this could be the Dockerfile.unstable flavor.

I'd not put in the same OBS package as the others as a flavor (we can include it in the github repository). The reason for that is because I'd love to be capable to keep OBS sources untouched when promoting from Dev to Staging to release projects. So if we keep development channel as a separate OBS image, then we can just simply do not submit it to release project and we are certain these bits are never landing in IBS.

The only thing I miss is when this image is refreshed. Can we for example trigger the elemental-channel service after build-baremetal-iso-image succeeds?

The idea is that no refresh is needed at all. Imagine something like:

registry.opensuse.org/isv/rancher/elemental/dev/containers/suse/sl-micro/6.0/baremetal-os-container:latest

This does not require refresh, it always pointing to the latest build we have in dev, which should be in sync with github repository head.

Otherwise the elemental-channels Github refresh action runs nightly, but for a development image I'd really love to always have the latest latest.

For development I don't think we need any refresh. They can be purely static, that's why I am not sure we need those sources in github repository at all.