Kubernetes Is Not a Platform: Building One with Juju

Installing Kubernetes is easy. Operating it across teams, under pressure, at scale that's where most organizations quietly struggle.

Clusters grow into a mix of manual kubectl workflows, inconsistent network policy, and operational knowledge nobody wrote down. It works until it doesn't.

The missing layer is operational lifecycle management and that's exactly what Juju was built for. Juju brings model-driven operations to Kubernetes: it manages service dependencies, handles upgrades and integrations, automates day-2 recovery, and encodes operational knowledge into reusable charms rather than fragile scripts and runbooks. Where most tools stop at deployment, Juju carries the operational story forward through the entire application lifecycle.

But a platform needs more than lifecycle automation. Delivery needs to be declarative and auditable that's where Argo CD fits in, providing GitOps-based deployment and drift control. And networking and security policy need to be enforceable at runtime that's where Cilium brings kernel-level policy enforcement and observability.

This session shows how Juju serves as the operational backbone of a Kubernetes platform, with Argo CD and Cilium filling the delivery and networking layers. Rather than presenting tools in isolation, the talk demonstrates a cohesive platform engineering model built around Juju's strengths in lifecycle automation and operational relationships.

Attendees will see how Juju's charm-based approach solves problems that GitOps alone cannot service integrations, cross-application dependencies, upgrade orchestration, and recovery workflows while Argo CD and Cilium handle what they do best.