K10 Multi-Cluster Manager¶
The K10 multi-cluster manager simplifies K10 operations across multiple Kubernetes clusters.
Administrators define primary-secondary relationships between their K10 instances. Primary K10 instances provide a single entry point and dashboard for administrators to manage secondary instances.
K10 resources, like Policies and Profiles, are defined in the primary instance and distributed to secondary instances. Secondary instances enact their policies and the secondaries' actions and metrics are summarized in the primary instance.
K10 installed on secondary clusters must be setup using token authentication.
The status of resources distributed to target clusters is not represented at a global level.
Modified global resources may not be re-distributed until the corresponding distribution resource is modified.
Resources distributed to target clusters will be overwritten when the global resource is re-distributed.
Modifications to resources distributed to target clusters will not be overwritten until the global resource is modified.
Multi-cluster configuration data is currently not protected by K10 Disaster Recovery. If clusters are recovered after disaster, re-bootstrapping of clusters is required.
For upgrades from versions 3.0.7 or lower to version 3.0.8 and higher, all clusters must be individually upgraded and all secondary clusters should be re-bootstrapped using the
k10multiclustertool. More information about bootstrapping can be found in the Bootstrapping Commands Reference section.