Skip to content

Latest commit

 

History

History
52 lines (31 loc) · 4.39 KB

README.md

File metadata and controls

52 lines (31 loc) · 4.39 KB
Raw

image

Welcome! The open-cluster-management.io project is focused on enabling end-to-end visibility and control across your Kubernetes clusters.

The Open Cluster Management (OCM) architecture uses a hub - agent model. The hub centralizes control of all the managed clusters. An agent, which we call the klusterlet, resides on each managed cluster to manage registration to the hub and run instructions from the hub.

You can use the clusteradm CLI to bootstrap a control plane for multicluster management. The following diagram illustrates the deployment architecture for OCM:

image

There are a number of key use cases that are enabled by this project, and are categorized to 3 sub projects.

Cluster Lifecycle: Cluster registration and management

OCM has a group of APIs to provide the foundational functions in multiple cluster management.

The journey of cluster management starts with Cluster Registration which follows a double opt-in protocol to establish a MTLS connection from the agent on the managed cluster (Klusterlet) to the hub (Cluster Manager). After this, users or operands on the hub can declare ManifestWorks which contains a slice of Kubernetes resource manifests to be distributed and applied to a certain managed cluster. To schedule workloads to a certain set of clusters, users can also declare a Placement on the hub to dynamically select a set of clusters with certain criteria.

In addition, developers can leverage Addon framework to build their own management tools or integrate with other open source projects to extend the multicluster management capability. OCM maintaines two built-in addons for application lifecycle and security governance. Users can also benefit from a Submariner addon, which automates the deployment and management of multi-cluster networking.

Application Lifecycle: Delivery, upgrade, and configuration of applications on Kubernetes clusters

  • Centrally create, update, and delete Kubernetes clusters across multiple private and public clouds.
  • Automatically deploy applications to specific clusters by subscribing to different workload (resource) channels, such as GitHub, Helm repository, ObjectStore, and resource templates.

The application model defines a Kubernetes-first way of describing the application. Your existing Kubernetes apps or kustomized apps can be adapted with the addition of a few new objects: Channel, and Subscription. Changes made to the app are then easily delivered to managed clusters based on the dynamic placement engine.

GRC: Governance, Risk and Compliance across Kubernetes clusters

  • Use prebuilt security and configuration controllers toto enforce policies on Kubernetes configuration across your clusters.

Policy controllers allow the declarative expression of a desired condition that can be audited or enforced against a set of managed clusters. Policies allow you to drive cross-cluster configuration or validate that a certain configuration explicitly does not exist.

The following repositories describe the underlying API and controllers for the GRC model:

Get connected

See the following options to connect with the community: