In my previous blog I wrote a detailed version describing how k0rdent eases platform engineering at scale.

For those of you who are unaware, k0rdent is a Kubernetes-native distributed container management environment (DCME) designed to help platform engineers manage infrastructure at massive scale. Built on Kubernetes’ maturity, stability, and wide adoption, k0rdent leverages community-driven standards to minimize adoption risks.

Acting as a “super control plane,” it enables centralized, template-driven lifecycle management of Kubernetes clusters and services across on-prem, cloud, and hybrid environments. By providing a repeatable, secure, and standardized approach, k0rdent empowers teams to compose Internal Developer Platforms (IDPs) that support complex modern workloads, while ensuring consistency and reliability.

The idea behind this blog is to cover more details on the latest k0rdent release v0.3.0 which went out on the 30th of April 2025 and aims to achieve increased clarity for developers to identify what is going on in the cluster, helps provide more visibility for all different components, and allows self-management of the mothership cluster.

We’re thrilled to announce the release of k0rdent v0.3.0, now available across the k0rdent Cluster Manager (kcm) and k0rdent Observability and FinOps (kof) components. This milestone brings significant enhancements focusing on observability, operational ease, and flexibility in infrastructure and service management.

Full documentation is available at: docs.k0rdent.io/v0.3.0

Key Highlights in v0.3.0

The latest release brings advancements to multi-cluster Kubernetes management, with enhanced observability and operational improvements.

Native Kubernetes events for observability

The release introduces native Kubernetes events emitted by core components:

These events offer transparency into system operations and support a new Cluster Deployment Dashboard for real-time visualization on the kof side.

Self-managed service templates

Service templates can now be defined and managed within the mothership cluster. This enhancement enables the following benefits:

Helm chart integration with Flux sources

Users can now install Helm charts using Flux sources such as GitRepository, Bucket, and OCIRepository through service templates. This update:

Dynamic infrastructure provider management

Enhanced support for infrastructure provider management introduces greater flexibility in hybrid environments. This includes:

Metrics and alerting enhancements

The release expands support for metrics and alerts collection across both mothership and regional kof storage clusters. Benefits include:

Stability and bug fixes

This release includes numerous improvements related to validation, performance, and bug resolution. Users can expect:

Learn more

Looking ahead

k0rdent v0.3.0 reinforces our mission to provide a robust, Kubernetes-native platform management framework. With enhanced observability, flexible service orchestration, and GitOps alignment, this release lays the groundwork for secure and scalable infrastructure operations.

We invite you to explore the release, engage with the project, and share your feedback via Slack or our GitHub repository.

Join the k0rdent community

Platform engineers today face increasing demands—but they don’t have to tackle them alone. k0rdent is 100% open-source and community-driven, offering the flexibility, tools, and ecosystem needed to manage distributed infrastructure efficiently.

Built by an international team of passionate developers, k0rdent thrives on collaboration. We welcome contributions and ideas to expand and improve the project.

Get Involved:

⭐️Drop a star to support the k0rdent project
✅ Explore the k0rdent Community repo on GitHub
✅ Join the #k0rdent channel on CNCF Community Slack (Sign up for CNCF Slack, then join #k0rdent)
✅ Sign up via our Community Invitation Form to attend Team k0rdent’s regular Office Hours

Be part of the movement—let’s build the future of Kubernetes-native infrastructure together!