Once a primary cluster is configured for the K10 Multi-Cluster Manager features can be accessed via the K10 Dashboard.
Dashboard And RBAC¶
The K10 Multi-Cluster Manager dashboard will be available at
/k10/#/clusters URL path of the DNS or IP address setup during
K10 install. Refer Dashboard Access for more information.
For users to be able to access the K10 Multi-Cluster Manager dashboard as well as other K10 Multi-Cluster features, additional role binding may be required.
k10-mc-admin ClusterRole is installed during K10 install/upgrade.
It is added for Distributions, Cluster Config,
K10 Config and Secrets access in the K10 multi-cluster namespace.
During bootstrapping, K10 creates a RoleBinding for a default Group
k10:admins in the K10 multi-cluster namespace. Admin users can be added
to this Group and will be able to use the above
k10-mc-admin will be installed under the name
This ClusterRole is not configurable and is installed with K10.
You can also create role bindings for existing users or service accounts.
To bind the
k10-mc-admin ClusterRole to a User, use the following command
$ kubectl create rolebinding <name> --clusterrole=k10-mc-admin \ --namespace=kasten-io-mc \ --user=<name>
To bind the
k10-mc-admin ClusterRole to a ServiceAccount, use the following
$ kubectl create rolebinding <name> --clusterrole=k10-mc-admin \ --namespace=kasten-io-mc \ --serviceaccount=<serviceaccount_namespace>:<serviceaccount_name>
- The complete RBAC reference can be found in the
K10 Multi-Cluster RBAC section.