Outcome Overview

Once all Features and/or Initiatives in this Outcome are complete, what tangible, incremental, and (ideally) measurable movement will be made toward the company's Strategic Goal(s)?

This is the overarching issue for tracking making OpenShift more composable. Specifically, we want to provide:
(1) a way with CVO to allow disabling and enabling of operators
(2) a way for OLM operators to be installed out of the box in OpenShift / by default as part of the cluster deployment using the OLM Subscription API 

Success Criteria

What is the success criteria for this strategic outcome?  Avoid listing Features or Initiatives and instead describe "what must be true" for the outcome to be considered delivered.

• Make the cost in dollars of running our control plane scale relative to the features a user wants by making components optional, to reduce operational expenses in public clouds.
• Make the resource consumption of our control plane scale relative to the features a user wants by making components optional, to reduce footprint in resource-constrained on-premise environments.
• Stop the growth of (and possibly reduce the size of) our core release payload and control plane footprint without sacrificing the ability to use features to customize the cluster at install-time.
• Break apart the current “all or nothing” monolithic nature of OCP clusters
• Customers to use smaller hosts for control plane nodes, in the cloud and in on-prem deployments, reducing their operational costs.
• Partners / resellers embedding OpenShift in applications, such as IBM Cloud Paks, to configure a deployment to provide only the features needed to run the application, improving resource consumption, operational costs, and security.
• Reduce the resource requirements for running OpenShift in constrained environments, such as single-node deployments.

Expected Results (what, how, when)

What incremental impact do you expect to create toward the company's Strategic Goals by delivering this outcome?  (possible examples:  unblocking sales, shifts in product metrics, etc. provide links to metrics that will be used post-completion for review & pivot decisions). {}For each expected result, list +what you will measure and when you will measure it (ex. provide links to existing information or metrics that will be used post-completion for review and specify when you will review the measurement such as 60 days after the work is complete)
 

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).