-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
rhcos: Support channels #1402
rhcos: Support channels #1402
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cgwalters If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Changes look good. Waiting for CI to return. |
48a3dda
to
349161f
Compare
Hum, no idea what went wrong there. /test e2e-aws |
Why would we have RHCOS channels? I thought we wanted to pull RHCOS from the release image, #1286. I think we want Cincinnati channels, not RHCOS channels. |
See also discussion in #1168. |
They already exist today, the installer just doesn't make them ergonomic to pull.
100% agreed! If we are all in agreement to land 1286 very soon I'm fine closing this. But if 1286 isn't going to go in in the next say day or two I'd like to land this so it's easier for others to test using our existing other streams. Once this lands it's totally fine to revert it in 1286 when rebasing. |
The code was hardcoded to `DefaultChannel`; add an environment variable so people (and CI) can use the other channels.
349161f
to
037d466
Compare
Yup, linked above too ;). And I still think that |
Superceded by #1423 |
The code was hardcoded to
DefaultChannel
; add an environment variableso people (and CI) can use the other channels.