Epic Goal

• As an OpenShift infrastructure owner, I need to be able to integrate the installation of my first on-premises OpenShift cluster with my automation flows and tools.
• As an OpenShift infrastructure owner, I must be able to provide the CLI tool with manifests that contain the definition of the cluster I want to deploy
• As an OpenShift Infrastructure owner, I must be able to get the validation errors in a programmatic way
• As an OpenShift Infrastructure owner, I must be able to get the events and progress of the installation in a programmatic way
• As an OpenShift Infrastructure owner, I must be able to retrieve the kubeconfig and OpenShift Console URL in a programmatic way

Why is this important?

• When deploying clusters with a large number of hosts and when deploying many clusters, it is common to require to automate the installations.
• Customers and partners usually use third party tools of their own to orchestrate the installation.
• For Telco RAN deployments, Telco partners need to repeatably deploy multiple OpenShift clusters in parallel to multiple sites at-scale, with no human intervention.

Scenarios

1. Monitoring flow:
   1. I generate all the manifests for the cluster,
   2. call the CLI tool pointint to the manifests path,
   3. Obtain the installation image from the nodes
   4. Use my infrastructure capabilities to boot the image on the target nodes
   5. Use the tool to connect to assisted service to get validation status and events
   6. Use the tool to retrieve credentials and URL for the deployed cluster

Acceptance Criteria

• Backward compatibility between OCP releases with automation manifests (they can be applied to a newer version of OCP).
• Installation progress and events can be tracked programatically
• Validation errors can be obtained programatically
• Kubeconfig and console URL can be obtained programatically
• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.

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>

References

• Bootable Ephemeral Installer Image for Disconnected Cluster 0 Deployments