Epic Goal

There are now two different versions of HyperShift CLI: developer version that exposes all arguments and external end-user version that exposes arguments that are only relevant for end-users.

The current Hypershift CLI exposes a lot of developer-only flags that are not applicable or recommended to use by end-users. The upstream hypershift team made changes such that the CLI binary can be built in two different ways to produce developer and end-user versions of the CLI.

This epic is to build and deliver the end-user version of CLI in MCE.

This epic is also about making the hypershift CLI binary available through some central place where all other OpenShift related binaries are also available so that cluster administrators can consistently download it along with everything else (oc, openshit-install) on Day 0 of the cluster deployment from the same place.

When upgrading the cluster, all CLI tools can be upgraded similarly and consistently via some automation.

Why is this important?

This epic clarifies the functionalities of the Hypershift CLI from MCE end-user perspective and hide confusing or irrelevant arguments that are only useful for backend code.

Scenarios

...

Acceptance Criteria

• The new downloadable CLI only exposes the end-user flags
• MCE documentation is updated to reference the new CLI command
• s390x CLI is available
• The CLI binaries are available at https://mirror.openshift.com/pub/openshift-v4/clients/ along with other tools
• The CLI binaries are also available through krew

Dependencies (internal and external)

1. (AWS platform currently not available in HCP CLI) https://issues.redhat.com/browse/HOSTEDCP-1017

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>