-
Notifications
You must be signed in to change notification settings - Fork 165
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
mantle/api: gcloud: remove FCOS specific image GuestOSFeatures #1333
mantle/api: gcloud: remove FCOS specific image GuestOSFeatures #1333
Conversation
This is a follow-up from #1319 (comment) |
We consider the VIRTIO_SCSI_MULTIQUEUE, UEFI_COMPATIBLE, and SECURE_BOOT flags to be standard now so we can unconditionally add them to GCP images we create and get rid of the --fcos option.
7b4045b
to
6e2ab0f
Compare
LGTM...I wrote all this stuff below then changed my mind, just attaching it for reference. I'm OK with this, though I think I'd vote instead we:
The idea here is it's slightly more convenienent for someone testing something interactively w/ore to pass |
Note that AFAICT this will change the defaults for the RHCOS pipeline. I'm guessing that openshift/installer#2921 only changes it at runtime when the instance is launched. |
No, as you discovered in internal chat, the openshift installer today always creates the image in GCP. That's precisely why that PR was needed (and indeed works without this one). |
/lgtm Thanks for the cleanup! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bgilbert, dustymabe 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 |
We consider the VIRTIO_SCSI_MULTIQUEUE, UEFI_COMPATIBLE,
and SECURE_BOOT flags to be standard now so we can
unconditionally add them to GCP images we create and get
rid of the --fcos option.