Open-cluster-management has a mechanism to help developers to develop an extension based on the foundation components for the purpose of working with multiple clusters in various asepcts. Examples of add-ons includes:
- A tool to collect alert events in the managed cluster, and send to the hub cluster.
- A network solution that uses the hub to share the network info and establish connection among managed clusters.
- A tool to spread security policies to multiple clusters.
In general, if a management tool needs a different configuration for each managed cluster or a secured communication between the managed cluster and the hub cluster, it can utilize the add-on mechanism in open-cluster-management to ease the installation and day 2 operation.
Each add-on should register itself on the hub by creating a
ClusterManagementAddon resource on the hub cluster. For instance, the
helloworld add-on can be registered to the hub cluster by creating:
kind: ClusterManagementAddOn metadata: name: helloworld spec: addOnMeta: displayName: helloworld
An add-on should also have a controller running on the hub taking responsible of add-on configuration for each managed cluster. When a user wants to enable the add-on for a certain managed cluster, the user should create a
ManagedClusterAddon resource on the cluster namespace. The name of the
ManagedClusterAddon should be the same name of the corresponding
ClusterManagementAddon. For instance, the following example enables
helloworld add-on in cluster1
kind: ManagedClusterAddon metadata: name: helloworld namespace: cluster1 spec: installNamespace: helloworld
Add-on framework provides a library for developers to develop an add-ons in open-cluster-management more easily. Take a look at the helloworld example to understand how the add-on framework can be used.