Epic: MCP Architecture v2 #15
Description
Understand the Epic
- Allow Service Provider to offer their software in MCP (extensibility)
- Run all operators in shared use (efficiency)
Context / Background
- Similar learning/paths learned from Kyma
User Stories or tasks
See below
What is required to accept the Epic as finished.
- Clear Design of Architecture V2 available
- Implementation done
Dependencies of this Epic
No response
Risks of this Epic
- This Epic is a huge investment. We have to make sure that progress is made transparent, and that we don't introduce changes which require existing MCP endusers to start from scratch, there has to be a migration path.
Known Stakeholders of this Epic
No response
Milestone Definitions for this Epic.
- MS1: New Design visualized and written down on a high-level, presented and agreed by the MCP Core team
- MS2: Definition of expected work / process for a human operator for an initial installation and day 2 of an MCP Landscape available as a document
- MS3: All required implementation tasks identified and technically defined, as well as refined (to enable planning). Roadmap planning finished, covering all individual tasks required to finish the Epic
- MS4: Implementation done
Metrics Definition for this Epic.
n/a
Any further valuable resources.
flowchart TD
dc[Define Cluster API]
cpkind[Implement Cluster API for Kind]
cpgard[Implement Cluster API for Gardener]
revc[Revisit Cluster API]
dc --> cpkind --> revc
dc --> cpgard --> revc
ds[Define Service Provider API]
spla[Implement Service Provider for Landscaper]
spcp[Implement Service Provider for Crossplane]
spocm[Implement Service Provider for OCM]
revs[Revisit Service Provider API]
ds --> spla --> revs
ds --> spcp --> revs
ds --> spocm --> revs