Platform Mesh Proof of Technology (PoT)¶
Overview¶
This section documents the findings of the Platform Mesh Proof of Technology (PoT) sprint (Epic: CLDAPI-26).
Goal: Evaluate whether the Platform Mesh (from NeoNephos Foundation) should be used as the foundation for building the Cloud API for ODC, or if the team should build a custom solution using KCP + Cloud API Operator directly.
User Stories¶
The PoT covers the following areas of investigation:
| ID | Topic | Status | Link |
|---|---|---|---|
| CLDAPI-42 | Infrastructure Components | ✅ Done | Analysis |
| CLDAPI-39 | ReBAC (OpenFGA) | ✅ Done | ReBAC |
| CLDAPI-40 | Portal + GraphQL | ⏳ Pending | Portal |
| CLDAPI-41 | IdP / IAM | ⏳ Pending | IdP / IAM |
| CLDAPI-43 | KCP Specifics | ⏳ Pending | KCP |
| CLDAPI-44 | Roadmap & Community | ✅ Done | Roadmap |
| CLDAPI-45 | Images, CVEs & Chainguard | ✅ Done | Security |
Decision Framework¶
The final decision will be based on the following criteria:
- Complexity vs. Value: Does Platform Mesh add necessary abstractions or unnecessary complexity?
- Maintenance Burden: Can we maintain the Platform Mesh components (OpenFGA, Traefik, etc.) ourselves?
- Community Health: Is the Platform Mesh community active and aligned with our roadmap?
- Security: Do the components meet our security standards (CVEs, Chainguard images)?
- Integration: How easily does it integrate with our existing stack (GitLab, Keycloak, KCP)?
Final Recommendation¶
Status: 🚧 Investigation in Progress
This section will be populated at the end of the PoT.
Pros¶
- ...
Cons¶
- ...
Conclusion¶
- ...