-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: RHCOS pipeline changes #652
Conversation
6068ec3
to
2e7b192
Compare
15b95cc
to
2e7b192
Compare
When rebasing onto #671, you'll want to rerun
And then rerun |
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. |
4f2490f
to
0cd5102
Compare
ff11ec6
to
46662e0
Compare
For testing purposes we can make |
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. |
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. |
It gets archived by directory name so it breaks if it is incorrect.
Signed-off-by: Renata Ravanelli <rravanel@redhat.com>
I think we can close this. |
This PR contains a rebase with main and
rhcos
branch