-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Automatic hub cluster deployment
-
False
-
-
False
-
Not Selected
-
To Do
Epic Goal
- Allow the user to deploy automatically the first hub cluster on Day 1
Why is this important?
- As initially described in https://github.com/openshift/installer/blob/master/docs/user/agent/mce-integration.md, there are a number of manual steps required to deploy an hub cluster. In particular, in addition to the MCE operator, it's required to install the Infrastructure operator and at least one storage operators - since it requires some persistent volumes to operate correctly
Scenarios
- See below
Acceptance Criteria
- Deploy an hub cluster without using any manual steps
Dependencies (internal and external)
Open questions::
- What's the best/recommended scenario for the automated storage configuration (see proposal below)?
- Is there any specific configuration where adding spoke clusters should be forbidden?
Automated storage configuration
- The Infrastructure Operator, a dependency of MCE to deploy bare metal, vSphere and Nutanix clusters, requires storage. There are 3 scenarios to automate storage:
- User selects to install ODF and MCE:
- ODF is the ideal storage for clusters but requires an additional subscriptions.
- When selected along with MCE it will be configured as the storage required by the Infrastructure Operator and the Infrastructure Operator will be deployed along with MCE.
- User deploys an SNO cluster, which supports LVMS as its storage and is available to all OpenShift users.
- If the user also chooses ODF then ODF is used for the Infrastructure Opertor
- If ODF isn't configured then LVMS is enabled and the Infrastructure Operator will use it.
- User doesn't install ODF or a SNO cluster
- They have to choose their storage and then install the Infrastructure Operator in day-
- is blocked by
-
AGENT-381 MCE installation from assisted operator plugin
- Closed