Some users have reported an issue in which a new cluster, provisioned via the DKP CLI and attached via the Kommander UI, gets stuck in a "Provisioned" state.
The new cluster appears to be completely up and healthy, but the loading icon in Kommander continues to spin and it never reaches a state where Kommander is managing it.
This is related to a known issue where external managed clusters are not automatically attached to Kommander. If you believe you are encountering this issue, you can verify it by listing the "KommanderCluster" objects in your Kommander management cluster:
kubectl get kommandercluster -A
If you do not see a KommanderCluster object that corresponds to the cluster and namespace of the cluster you are trying to add, you can apply the object manually as a workaround. Save this as a file and call it something like kommander-cluster.yaml:
---
apiVersion: kommander.mesosphere.io/v1beta1
kind: KommanderCluster
metadata:
annotations:
kommander.mesosphere.io/display-name: "${CLUSTER_NAME}"
name: "${CLUSTER_NAME}"
namespace: "${NAMESPACE}"
spec:
kubeconfigRef:
name: ${CLUSTER_NAME}-kubeconfig
clusterRef:
capiCluster:
name: ${CLUSTER_NAME}
Make sure you replace CLUSTER_NAME and NAMESPACE with the name and namespace that you assigned to the cluster you are attempting to attach, or declare them as envvars before applying it with:
kubectl apply -f kommander-cluster.yaml
Once the object has been applied, the cluster should attach as expected.