-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
-
UI work for for enabling UEFISecureBoot for VMs (as required by ShieldVM policy) for OSD in GCP
-
True
-
-
False
-
To Do
-
XCMSTRAT-115 - [OSD RFE] Enable UEFISecureBoot for VMs (as required by ShieldVM policy) for OSD in GCP
-
0% To Do, 0% In Progress, 100% Done
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), via the OCM UI.
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.
- is blocked by
-
PD-1591 UX design for enabling UEFISecureBoot for VMs (as required by ShieldVM policy) for OSD in GCP
- Closed
1.
|
DOD: Training materials supplied to Support/SRE | To Do | Unassigned | ||
2.
|
DOD: Docs verified by QE | To Do | Unassigned | ||
3.
|
DOD: Docs completed and merged | To Do | Unassigned | ||
4.
|
DOD: All known issues captured and blockers resolved | To Do | Unassigned | ||
5.
|
DOD: All work items belonging to this Epic are complete | Closed | Unassigned | ||
6.
|
DOD: Code merged for regular build/release testing in the HAC Common CI/CD framework | To Do | Unassigned | ||
7.
|
DOD: CI runs successfully with test automation | To Do | Unassigned | ||
8.
|
DOD: Automated/Integrated tests complete | To Do | Unassigned | ||
9.
|
DOD: Architectural artifacts completed, reviewed and stored | To Do | Unassigned | ||
10.
|
DOD: Product Manager and UX signed off on solution | To Do | Unassigned | ||
11.
|
DOD: Acceptance criteria related to this Epic has been identified and met | To Do | Unassigned |