Epic: Composition Functions for Releasechannels #32
Description
Understand the Epic
We want to support Composition Functions as managed components to be added to a releasechannel.
Context / Background
This helps to provide compliant composition functions to our customers so they can be sure to use compliant components without needing to evaluate them on their own.
User Stories or tasks
- I as a user of an MCP landscape want to install common/well-known composition functions when ordering an MCP
- I as an operator of an MCP landscape want to mirror composition functions into end-user owned OCI registry.
What is required to accept the Epic as finished.
- Composition Functions must be addable to an releasechannel
- Composition Functions must be OCM components
- Composition Functions must be pushed into the OCM releasechannel registry
- Composition Functions must be mirrored internally
Dependencies of this Epic
No response
Risks of this Epic
- complexity when implementing composition functions into the control plane operator as a managed components, needs to be evaluated with @ValentinGerlach as the new MCP v2 could reduce that complexity
- compliance process not yet finished in releasechannel repo (separate epic ...) could potentially have an impact
Known Stakeholders of this Epic
- operators of MCP landscapes
- users of MCP landscapes
Milestone Definitions for this Epic.
- Composition Functions can be added to releasechannel
- Composition Functions can be installed in MCP landscapes when ordering a MCP
Metrics Definition for this Epic.
- adoption of composition functions in Releasechannel deployments
Any further valuable resources.
- control plane operator needs to support it (depends on MCP v2)