-
Initiative
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
Proactive Architecture
-
False
-
-
False
-
0
*Outcome Overview*
A supported procedure for migrating an existing on premises control planes to a hosted control plane enables customers to achieve the benefits of hosted control planes without have to start new projects to take advantage of the new architecture, or come up with a plan on their own that we don't support. The outcome can be measured by the number of hosted control planes that report telemetry over time (just like hcp adoption).
*Success Criteria*
There must be a procedure to migrate a classic control plane (enumerations of starting configurations are fine and expected) to a hosted control plane where the supporting stakeholders (Service Delivery, OCP engineering, support, qe, etc) are comfortable in accepting support responsibilities for the actions recommended.
TODO: ensure the list of stakeholders is sufficient
*Expected Results (what, how, when)*
The number of existing classic clusters will trend downward while the number of hosted control planes will trend upward within an account. I expect the pace to perform migrations will be fairly slow, so quarterly reporting is likely sufficient.
TODO: find links to existing control plane count dashboardsÂ
*Post Completion Review – Actual Results*
After completing the work (as determined by the "when" in Expected Results above), list the actual results observed / measured during Post Completion review(s).
- relates to
-
MIG-1340 Add support for Hypershift with MTC
- New