OpenClusterManagement 0.7 Highlights: DefaultClusterSet, v1beta1 Placement API, Hosted Mode

Release Overview

OpenClusterManagement (OCM) 0.7 was released at the end of March, bringing a set of new capabilities and bug fixes for a smoother multi‑cluster experience.

DefaultClusterSet

The new DefaultClusterSet feature automatically registers every managed cluster into a ClusterSet named “default”. Previously users had to create a ClusterSet topology manually before accessing advanced features such as Placement. With the default set, a simple “default” → central cluster binding enables immediate multi‑cluster orchestration.

Placement API v1beta1

Based on community feedback from the v1alpha1 release, the Placement API has been promoted to v1beta1. The beta version guarantees better API compatibility and introduces support for Taint/Toleration‑based multi‑cluster scheduling, allowing users familiar with native Kubernetes scheduling to apply similar concepts across clusters.

Hub Cluster Version Requirement

The required Kubernetes version for the Hub cluster has been lowered from 1.19 to 1.12. This is possible because OCM now supports the beta CSR API. Enabling the compatibility requires adding the following feature gate to the registration component:

--feature-gate=V1beta1CSRAPICompatibility=true

Hosted Deployment Mode

OCM’s default “hub‑spoke” mode deploys an Agent controller (Klusterlet) on each managed cluster. The new Hosted mode moves the Agent controller to the central Hub, eliminating the need for additional components on managed clusters.

Integration with KubeVela 1.3

KubeVela 1.3 deepens its integration with OCM, providing sample guides and a demo repository at https://github.com/oam-dev/samples/tree/master/12.Open_Cluster_Management_Demo. Users can:

Deploy OCM Hub components via a KubeVela plugin.

Deploy Klusterlet agents on managed clusters using the vela CLI.

Experience KubeVela’s multi‑cluster application publishing features.

Alibaba Cloud ACK Agile Edition

The ACK Agile edition now ships with OCM’s multi‑cluster gateway plugin. Documentation links allow users to quickly try the integration, enabling the Hub to reach managed clusters across any network while rotating client certificates for security. Users can also register local Kind clusters to a cloud‑based OCM Hub for forward API access.

Getting Started

New users should follow the quick‑start guide (https://open-cluster-management.io/getting-started/quick-start/), while existing 0.6 users can refer to the upgrade documentation (https://open-cluster-management.io/getting-started/administration/upgrading/). Detailed concepts about ClusterSet topology are available at https://open-cluster-management.io/concepts/managedclusterset/.