For multi-cluster features to function properly,
ingress for the primary cluster needs
to be configured. The ingress must be specified as the full URL used to access
the K10 dashboard, e.g.
This can be done by editing the Cluster resource for the primary cluster,
and setting the
spec.k10.ingress.url field using
kubectl edit -n kasten-io-mc cluster <PRIMARY_CLUSTER>
To enable License Management feature, the ingress for the primary cluster needs to be configured.
Refer to the v6.5.0 upgrade note for how to set the ingress for the primary cluster, which is required for all multi-cluster features from v6.5.0 onward.
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
k10multicluster tool. More information about
bootstrapping can be found in the Bootstrapping Commands Reference section.