Building Europe's Cloud Future: NeoNephos' Platform Mesh
summary
Platform Mesh claims to standardize a multi‑provider cloud‑edge continuum by treating every service as a Kubernetes digital twin and using the Kubernetes resource model as a common API. The prototype uses KCP, kube-bind, multicluster‑runtime, API sync agents and virtual workspaces to order a MongoDB service and a KMA Kubernetes instance from different providers, copy secrets across control planes, deploy an app and successfully connect it to the remote DB, demonstrating reduced vendor lock‑in and orchestration via declarative KRM manifests.
AI-written summary · about
chapters (15)
- 0:00NeoNephos and Platform Mesh intro
- 1:24Cloud edge continuum challenges
- 6:22Standardizing cloud with Kubernetes
- 8:26Platform Mesh with KCP
- 10:12Demo: Order services across providers
- 16:54Benefits of common K8s language
- 18:40Kubernetes Resource Model
- 22:31Why adopt Platform Mesh
- 26:04Provider and consumer views
- 30:01Future directions and open source
- 31:05Q&A: Access control
- 32:14Q&A: Provider risks
- 33:42Q&A: Platform Mesh clarifications
- 36:30Q&A: CI/CD integration
- 38:05Q&A: Platform infrastructure
related talks
20mCloud Sovereignty: Introducing the NeoNephos Linux Foundation Europe Project
35mOrchestrating Interconnected Apps Across Geographically Distributed Kubernetes Clusters
16mThe Sovereignty Blueprint: Multi-Cloud Platform Strategy for European Ecosystem
43mPlatform Engineering Redefined: Evolving Kubernetes Beyond Container Orchestration
15mNeoNephos: Building a Sovereign Cloud Native Technology Stack
27mBuilding an Edge Computing Platform for Network Services Using Cloud Native Technology [I]
29mNeoNephos’ OpenControlPlane: Building Europe’s Next-Gen Control Plane-as-a-Service.
34mTaking Back Control: Building Cloud-Agnostic Container Platforms for Regulated Environments