-
Epic
-
Resolution: Done
-
Undefined
-
UX design for enabling UEFISecureBoot for VMs (as required by ShieldVM policy) for OSD in GCP
-
False
-
None
-
False
-
To Do
-
XCMSTRAT-115 - [OSD RFE] Enable UEFISecureBoot for VMs (as required by ShieldVM policy) for OSD in GCP
-
-
-
Admin UXD sprint 244, Admin UXD Sprint 245
This is a placeholder ticket for providing admins the flexibility to provision the OSD clusters on GCP with and without UEFISecureBoot (i.e. with or without "constraints/compute.requireShieldedVm" policy).
For more details on the feature, refer XCMSTRAT-115
Update, July 17, 2023 (post discussion with SREPs)
- Enabling Secure Boot by default can impact the ability to load GPU drivers if they are unsigned. Ref: https://cloud.google.com/compute/docs/gpus/install-drivers-gpu#secure-boot]
- Therefore, it was decided to have admin users explicitly opt in for "platform.gcp.defaultMachinePlatform.secureBoot" when provisioning the OSD cluster on GCP. This is assumed to be enabled/disabled by a new field in the OCM UI.
- Based on whether "platform.gcp.defaultMachinePlatform.secureBoot" is enabled or disabled, the admin must ensure "constraints/compute.requireShieldedVm" policy is in or NOT in place in the GCP console.
Background: Before implementing this feature, the admin must ensure "constraints/compute.requireShieldedVm" policy is NOT place as listed in the OSD documentation.
Design doc: https://docs.google.com/document/d/1TOJieI8P34hIqZsgMSbdklSSc3r7WHEM1mJRGcPPYBM/edit?usp=sharing
- blocks
-
OCMUI-135 UI work for for enabling UEFISecureBoot for VMs (as required by ShieldVM policy) for OSD in GCP
-
- Closed
-