Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-98

Updated boot images: Phase 1 - GCP Tech Preview

    XMLWordPrintable

Details

    • Feature
    • Resolution: Unresolved
    • Critical
    • None
    • None
    • OS
    • False
    • Hide

      None

      Show
      None
    • False
    • 21
    • 21% 21%
    • 0
    • 0

    Description

      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

      Attachments

        Issue Links

          is cloned by

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-1170 Updated boot images: Phase 2 (GCP GA, Other platforms TP)

          • Critical - To be worked on immediately following BLOCKER issues.
          • New
          is related to

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-15087 /sysroot mountpoint failed to resize automatically on new nodes during machineset scaleup

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-4769 Old AWS boot images vs. 4.12: unknown provider 'ec2'

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-9969 4.1 born cluster fails to scale-up due to podman run missing `--authfile` flag

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Spike - Represents a research-related task. MCO-567 Investigate boot image update requirement

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Activity

            People

              rhn-support-mrussell Mark Russell
              rhn-support-mrussell Mark Russell
              Matthew Werner Matthew Werner
              Derrick Ornelas Derrick Ornelas
              Votes:
              2 Vote for this issue
              Watchers:
              27 Start watching this issue

              Dates

                Created:
                Updated: