Uploaded image for project: 'OpenShift Hosted Control Plane'
  1. OpenShift Hosted Control Plane
  2. HOSTEDCP-1104

Fail CLI early if the release image is not multi-arch and the management cluster's CPU architecture is not the same as the NodePool's CPU architecture

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • Hypershift Sprint 250, Hypershift Sprint 251, Hypershift Sprint 252, Hypershift Sprint 253
    • 0
    • 0
    • 0

      User Story:

      As a user of the HyperShift CLI, I would like the CLI to fail early if these conditions are all true:

      • the release image is not multi-arch
      • the management cluster's CPU architecture is not the same as the NodePool's CPU architecture

      so that we can prevent a HostedCluster from being created that will have errors due mismatches between the release image, management cluster's CPU architecture, and NodePool's CPU architecture.

      Acceptance Criteria:

      • The HyperShift CLI fails to create a cluster when the release image is not multi-arch and the management cluster's CPU architecture does not match the NodePool's CPU architecture.
      • There is documentation providing information the CLI will fail when it meets the conditions above.

      (optional) Out of Scope:

      This should be done for the API as well but will be covered thru HOSTEDCP-1105.

      Engineering Details:

      • HyperShift CLI currently defaults to a multi-arch image in version.go.

      This requires/does not require a design proposal.
      This requires/does not require a feature gate.

            rh-ee-brcox Bryan Cox
            rh-ee-brcox Bryan Cox
            Liangquan Li Liangquan Li
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: