Uploaded image for project: 'OpenShift Installer'
  1. OpenShift Installer
  2. CORS-4297

Installer GCP N4A machine types support

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • openshift/installer
    • None
    • Installer GCP N4A machine types support
    • In Progress
    • Product / Portfolio Work
    • OCPSTRAT-2664GCP N4A machine types support
    • 36% To Do, 18% In Progress, 45% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • Hide

      January 20, 2026 - The Epic is progressing and has been tested by multiple users. N4A instances are able to be created for both control plane and compute nodes. Custom machine types are also capable of being used (see snippet below):

       

      compute:
- architecture: arm64
  hyperthreading: Enabled
  name: worker
  platform:
    gcp:
      osDisk:
        diskSizeGB: 200
        diskType: hyperdisk-balanced
      type: n4a-custom-15-37888
  replicas: 3

       

      The only outstanding questions for now are the available disk types. Currently only hyperdisk-balanced is supported in openshift. The disucssion here has more information about hyperdisk-throughput and hyperdisk-balanced-high-availability. These would be handled by the storage team probably but the installer would have to add values for supported types if these do become supported.

       

      Show
      January 20, 2026 - The Epic is progressing and has been tested by multiple users. N4A instances are able to be created for both control plane and compute nodes. Custom machine types are also capable of being used (see snippet below):   compute: - architecture: arm64   hyperthreading: Enabled   name: worker   platform:     gcp:       osDisk:         diskSizeGB: 200         diskType: hyperdisk-balanced       type: n4a-custom-15-37888   replicas: 3   The only outstanding questions for now are the available disk types. Currently only hyperdisk-balanced is supported in openshift. The disucssion here has more information about hyperdisk-throughput and hyperdisk-balanced-high-availability. These would be handled by the storage team probably but the installer would have to add values for supported types if these do become supported.  
    • M
    • None
    • None

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • Qualify and support `n4a-*` machine types for control plane and worker nodes where applicable.
      • Expose N4A/custom machine types via installer configuration (platform.gcp) and Machine API (MachineSets/NodePools providerSpec) for day-1/day-2.
      • Ensure payload and images support ARM64/aarch64 where required (e.g., RHCOS aarch64 on GCP; multi-arch payload readiness).
      • Validate Cluster Autoscaler compatibility with N4A/custom shapes.
      • Publish documentation for install/operations on N4A and custom shapes.
      •  

      Why is this important?

      • N4A instances are new to GCP. These instances offer new arm support

      Scenarios

      1. ...

      Acceptance Criteria

      • Users can select N4A/custom shapes in install-config and via MachineSets/NodePools.
      • Clusters successfully provision and operate on N4A-based nodes; autoscaling and MHC function correctly.
      • Required aarch64 images/payloads available and validated where applicable.
      • Docs published with configuration examples and limitations.
      •  

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions::

      1. ...

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              rh-ee-bbarbach Brent Barbachem
              rh-ee-bbarbach Brent Barbachem
              None
              None
              Jianli Wei Jianli Wei
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: