This article is based on pre-event briefings conducted for KubeCon Europe 2020, which was postponed by the Cloud Native Computing Foundation (CNCF) due to the COVID-19 pandemic. Original analysis sourced from SiliconAngle.
Background: KubeCon Europe 2020 Goes Virtual
KubeCon + CloudNativeCon Europe 2020 was scheduled to draw thousands of cloud-native engineers and architects to Amsterdam. Like most major tech conferences in early 2020, the CNCF postponed the in-person event in response to the COVID-19 outbreak. Despite that disruption, vendors did not slow their roadmaps. Briefings shifted to remote sessions, and the product launches and partnerships planned for the show went ahead regardless.
The following six companies — selected from a field of roughly 75 exhibitors — represent a cross-section of the Kubernetes ecosystem in 2020: managed data infrastructure, container image security, hybrid service meshes, edge networking, API governance, and large-scale cluster automation. A unifying theme runs through all of them: enterprise-grade commercial offerings built on a foundation of open-source technology.
1. Aiven: Fully Managed Open-Source Data Infrastructure
Building and maintaining complex data pipelines across multiple clouds is a significant operational burden. Aiven addresses this by offering a fully managed “data cloud” that combines popular open-source data technologies — including Apache Kafka, PostgreSQL, Elasticsearch, Apache Cassandra, and Grafana — and deploys them across the major public cloud providers.
Instead of provisioning, configuring, and integrating each component individually, engineering teams can select the tools they need and the cloud regions they prefer. Aiven handles the operational layer: resilience, compliance, security patching, and cross-cloud connectivity. This model is particularly relevant for teams running Kubernetes-based microservices architectures that rely on heterogeneous data back-ends.
Why it matters
Managed open-source services reduce the toil of database operations without locking teams into a single cloud vendor’s proprietary data products. The multi-cloud, multi-tool flexibility aligns well with the principles underpinning cloud-native architecture.
2. Anchore: Shift-Left Security for Docker Images
“Shift left” is a well-worn phrase in DevSecOps, but most tools that claim to shift security earlier in the pipeline focus on source code scanning. Anchore takes a different approach: it works directly with Docker images — the declarative artifacts that define how containers are built and deployed.
Anchore inspects every layer of a container image, including:
- File system contents and installed packages
- Network configuration and exposed ports
- Build environment metadata
- Software bill of materials (SBOM)
Policy constraints are applied to images before they reach production. Those policies are then enforced at runtime in the Kubernetes environment, ensuring that only images meeting defined security criteria can run. This approach addresses a gap that pure source-code scanners miss: vulnerabilities introduced by base images or build-time dependencies that have nothing to do with application code.
Why it matters
Container image security is distinct from application code security. Scanning images at build time and enforcing policies at runtime provides defense in depth across the full container lifecycle — a critical requirement for regulated industries running workloads on Kubernetes.
3. Decipher Technology Studios: Hybrid Service Mesh with Grey Matter
Service meshes solve real problems in Kubernetes environments: abstracting network complexity for inter-service communication, handling ingress and egress routing, enforcing traffic policies, and providing observability. The catch is that most service mesh solutions are designed exclusively for greenfield, Kubernetes-native workloads.
Decipher Technology Studios built Grey Matter to work across both greenfield (cloud-native) and brownfield (legacy) applications, on Kubernetes and non-Kubernetes infrastructure alike. Grey Matter is built on Envoy, the widely adopted open-source proxy that also underpins Istio and other mesh implementations.
Key design principles in Grey Matter include:
- Hybrid reach: Service mesh capabilities extend to on-premises environments, not just public cloud.
- Operator flexibility: Sensible defaults reduce operational complexity, but granular policy configuration remains available for teams that need it.
- Out-of-process policy enforcement: Network policies are applied outside the application process to avoid adding latency to service calls.
Why it matters
Most enterprises cannot afford to migrate all workloads to Kubernetes simultaneously. A service mesh that spans both legacy and cloud-native environments allows organizations to adopt mesh capabilities incrementally, without requiring a complete architectural re-platform first.
4. Kaloom: Cloud-Native Network Fabric for Edge and 5G
The telecom industry spent years pursuing Network Functions Virtualization (NFV) and Virtual Network Functions (VNFs) as the path to software-defined networking. The results were mixed at best. Kaloom takes a different approach, building a programmable, automated edge data center fabric aligned with cloud-native principles and the emerging Cloud-Native Network Functions (CNF) model, which uses Kubernetes as the deployment and orchestration layer.
Kaloom’s platform is designed to span multiple network tiers:
- Enterprise and telco core networks
- Edge and access networks
- Device endpoints (IoT, industrial sensors)
The platform targets two high-growth use cases: 5G network rollouts, which demand low-latency, high-throughput programmable networking; and AI-driven edge applications, including IoT workloads that require compute to run close to data sources rather than in centralized cloud regions.
Why it matters
5G and edge computing are driving demand for network infrastructure that can be managed and orchestrated using the same cloud-native tooling — including Kubernetes — that development teams already use. CNFs represent a significant shift for telecom operators who need programmable, scalable networks without the lock-in of proprietary hardware or legacy VNF stacks.
5. Kong: API Gateway and Service Mesh for Distributed Interface Governance
Kong is often described as an API gateway platform for multi-cloud and hybrid environments. While accurate, that description undersells what Kong was positioning at KubeCon 2020. The more complete picture includes Kuma, Kong’s open-source service mesh, and the company’s broader concept of a Service Control Platform.
The traditional distinction in distributed systems is:
- North-south traffic: Communication between external clients and internal services — historically the domain of API gateways.
- East-west traffic: Communication between microservices within the same environment — the domain of service meshes.
Kong’s position is that this boundary is artificial. Whether traffic flows north-south or east-west is a matter of context and policy, not a hard architectural line. By combining a distributed API gateway with Kuma’s service mesh capabilities, Kong aims to provide unified governance across all service-to-service and client-to-service communication, regardless of direction or environment.
This is practically relevant for microservices architectures where the same service may act as a consumer in one context and an exposed API endpoint in another. Enforcing consistent authentication, rate limiting, observability, and routing policies across all interactions — through a single control plane — simplifies governance at scale.
Why it matters
As organizations scale microservices deployments, managing separate API gateway and service mesh tooling creates operational overhead and policy fragmentation. A unified platform reduces that complexity while enabling consistent security and traffic management across hybrid and multi-cloud environments.
6. Loodse: Automating Kubernetes Cluster Operations at Scale with Kubermatic
Running a single Kubernetes cluster is a manageable problem. Running hundreds or thousands of clusters across public cloud, on-premises data centers, and edge locations — consistently and reliably — is an entirely different challenge. Loodse built the open-source Kubermatic Kubernetes Platform specifically to address this operational problem.
Kubermatic automates both the provisioning and ongoing operations of Kubernetes clusters at scale. Key capabilities include:
- Multi-environment support: Works across all major public clouds, on-premises infrastructure, and edge deployments.
- Graduated automation: Teams can start with human-assisted operations and progressively move toward fully automated, lights-out management.
- Enterprise blueprints: Governance templates that encode organizational policy into cluster configuration, ensuring that compliance and security constraints are applied consistently across all clusters.
- Kubernetes Operator pattern: Kubermatic itself is built using the Kubernetes Operator pattern, meaning cluster lifecycle management is expressed as Kubernetes-native custom resources — consistent with cloud-native best practices.
Why it matters
For large enterprises and managed service providers running Kubernetes at scale, manual cluster operations do not scale. The operational burden of patching, upgrading, and enforcing policy across hundreds of clusters requires automation. Kubermatic’s intent-based governance model also aligns cluster configuration with business policy, reducing drift and compliance risk.
Key Takeaway: Enterprise Open Source Is Maturing
A consistent pattern runs across all six vendors: commercial enterprise offerings built directly on top of open-source foundations. These are not companies bolting proprietary layers onto unrelated open-source projects. Aiven manages open-source data tools. Anchore extends container image analysis. Decipher builds on Envoy. Kaloom advances CNF standards. Kong maintains Kuma. Loodse drives Kubermatic.
The traditional critique of open source in the enterprise — that it delivers components but not complete, supportable solutions — is increasingly outdated. The cloud-native ecosystem has reached a level of maturity where organizations can adopt open-source infrastructure with enterprise-class security, compliance, scalability, and support built in, without sacrificing the flexibility and community transparency that made those technologies compelling in the first place.
For DevOps and platform engineering teams evaluating Kubernetes tooling, the practical implication is straightforward: the best solutions in this space are those that contribute to the open-source projects they depend on, not those that merely consume them.