On Wed, May 15, 2024 at 8:58 AM Colin Walters walters@verbum.org wrote:
On Tue, May 14, 2024, at 4:30 PM, Troy Dawson wrote:
Everything else is "stream9". Names, directories, alot of things. Halfway through a products lifecycle doesn't seem like the time to streamline things.
Yeah, agreed.
Other than that, I think this looks good.
OK so, any who can own/help with that? Right now we have a Konflux pipeline. Ideally in the more medium term, we share procedures with whatever produces quay.io/centos/centos:stream9. And speaking of, what does produce that now and where is its source?
I think we should, as a project, look more earnestly at Konflux itself. That would likely be better than the existing tooling we have for building containers today.
You are correct, we need to either update this each time the latest container is updated (currently stream9) or remove it. Can you open a Jira issue against the CentOS Stream Pipeline team.
https://issues.redhat.com/browse/CS-2159
On a related subject. Do you see this work being transferred to the CentOS Stream team when it comes out of tech preview? They are the team that makes the containers.
Yes - but we'll need to bear in mind this container is very actively developed and has a lot more going on related to it than the existing "app" base image, so in practice the team working on it would need to be working at least pretty closely with any other release engineering teams.
I don't understand how Tech Preview in RHEL matters in terms of who is building the images. Support stance in RHEL is irrelevant in Stream. The work has to happen either way.
josh