-
Feature
-
Resolution: Done
-
Critical
-
None
-
BU Product Work
-
False
-
-
False
-
0% To Do, 0% In Progress, 100% Done
-
0
-
Program Call
Feature Overview
OCP 4 clusters still maintain pinned boot images. We have numerous clusters installed that have boot media pinned to first boot images as early as 4.1. In the future these boot images may not be certified by the OEM and may fail to boot on updated datacenter or cloud hardware platforms. These "pinned" boot images should be updateable so that customers can avoid this problem and better still scale out nodes with boot media that matches the running cluster version.
Phase one: GCP tech preview
- is cloned by
-
OCPSTRAT-1170 Updated boot images: Phase 2 (GCP GA, AWS TP)
- Closed
- is related to
-
OCPBUGS-15087 /sysroot mountpoint failed to resize automatically on new nodes during machineset scaleup
- Closed
- relates to
-
OCPBUGS-4769 Old AWS boot images vs. 4.12: unknown provider 'ec2'
- Closed
-
OCPBUGS-9969 4.1 born cluster fails to scale-up due to podman run missing `--authfile` flag
- Closed
-
MCO-567 Investigate boot image update requirement
- Closed