---
title: "KubeCon London 2025 Recap: Cloud-Native Insights on Security, Wasm, and More"
description: "KubeCon London 2025 showed a cloud-native ecosystem shifting from fragmentation to unification of policy, security, observability, and artifact management."
canonical_url: "https://cloudsmith.com/blog/kubecon-london-2025-insights"
last_updated: "2025-04-07T17:42:56.000Z"
---
# KubeCon London 2025 Recap: Cloud-Native Insights on Security, Wasm, and More

****TL;DR****: KubeCon London 2025 (KubeCon EU) showed a cloud-native ecosystem shifting from fragmentation to unification of policy, security, observability, and artifact management. Wasm is moving from hype to real-world use, OPA is expanding into FinOps, and signing everything (with SBOMs, attestations, and metadata) is becoming standard. Artifact registries are evolving fast, becoming unified platforms for governance, provenance, and automation across the software supply chain.

****TL;DR****: Wasm is no longer experimental — it’s powering plugins, policy engines, and serverless runtimes in real deployments. Tools like wasmCloud and Spin are leading the way.

****TL;DR****: Security was the dominant theme at KubeCon 2025. Signing, provenance, and secure-by-default registries were front and center. Tools like TUF, Notary, ORAS, and Kyverno are key to verifying that every artifact in your cluster is trusted.

****TL;DR****: Observability took center stage, pushing to unify metrics, logs, and traces via a standard query language and better tooling. Real-time insight is becoming essential for security, performance, and cost optimization.

****TL;DR: ****Open Policy Agent remains central to security policy but is now expanding into cost optimization. If you’re already using Gatekeeper, adding custom FinOps policies is an easy next step — and increasingly a product expectation for cloud-native solutions.

****TL;DR: ****Artifact registries are evolving to meet new expectations for provenance, automation, and cost efficiency. Talks focused on treating all artifacts as OCI-native, aligning with SLSA, and integrating retention and security as standard.