WIP: RHCOS pipeline changes

[ravanelli]

This PR contains a rebase with main and rhcos branch

[jlebon]

With the first commit in #666, you should be able to just add yumrepos to the config YAML and drop b0e4350.

[jlebon]

When rebasing onto #671, you'll want to rerun jenkins.yaml using something like this:

oc process --filename=manifests/jenkins.yaml --param=NAMESPACE=... ... | oc replace -f -

And then rerun ./deploy as well and start another build of jenkins-agent.

[dustymabe]

When rebasing onto #671, you'll want to rerun jenkins.yaml using something like this:

oc process --filename=manifests/jenkins.yaml --param=NAMESPACE=... ... | oc replace -f -

And then rerun ./deploy as well and start another build of jenkins-agent.

Honestly I'm thinking with all the recent changes we need to do wipe the entire namespace and start from scratch. Will give us good confidence that our "initial deployment" steps are in a good place. This probably needs to be coordinated amongst several of us. For example all of the secrets that currently exist in bitwarden need to be updated.

[cgwalters]

For testing purposes we can make quay.io/rhel-coreos-devel or whatever right? I imagine we could also ask DPTP to run a quay instance in the CI cluster...

[jlebon]

For testing purposes we can make quay.io/rhel-coreos-devel or whatever right? I imagine we could also ask DPTP to run a quay instance in the CI cluster...

Right, we could do that. I'd prefer pushing to a namespace that already exists though so we don't have to manage yet another account somewhere and track its credentials, etc... If that doesn't exist, creating one sounds fine.

[cgwalters]

Related to this though, I have some more work in the background for coreos/coreos-assembler#2685 which as you know turns this all on its head - the canonical source of truth is a container image, so in this model a registry is required, s3 is optional.

[jlebon]

I think we can close this.