Building Agentic-Ready Infrastructure with kcp Workspaces and API Export
summary
Shows that kcp workspaces provide workspace-level API isolation and that Google ADK can auto-discover kcp OpenAPI specs so an agent sees only bound APIs. Uses API export/binding to publish services; a sync agent pushes requested resources to a provider cluster where an operator (Python) actually provisions databases. Live demo: agent successfully creates a DNS record but a database request is rejected because the app workspace has no binding. Notes CRD descriptions can be prompt-injection risks.
AI-written summary · about
chapters (6)
- 0:00Introduction and motivation
- 6:05What is KCP and why it matters
- 10:02API exports and bindings in KCP
- 16:11Demo setup and architecture
- 28:25Live demo and agent interaction
- 33:22Resources and community
related talks
32mBuilding a Platform Engineering API Layer with kcp
34mBuilding a Platform Engineering API Layer with KCP
27mBuilding a Platform Engineering API Layer with kcp
01h 15mTutorial: Exploring Multi-Tenant Kubernetes APIs and Controllers With Kcp
27mBeyond Chat: Bringing Agents To Kubernetes
41mKcp: Towards 1,000,000 Clusters, Name^WWorkspaced CRDs
54mCreate Multi-Agent Systems with ADK
01h 09mMulti Agent Architecture using ADK