Skip to main content
Skip table of contents

Errors Related to CAPI Resources

Failed Condition Reason: FailedToIdentifyCAPIResources

kubeconfigRef points to the wrong secret

Verify the KommanderCluster object of both your Essential and Enterprise clusters. The spec.kubeconfigRef.name of each object should point to a valid kubeconfig secret.

  1. Download the referenced kubeconfig to your local machine:

    CODE 
    kubectl get secret -n <WORKSPACE_NAMESPACE> <cluster_name>-kubeconfig -o jsonpath='{.data.value}' | base64 --decode > <cluster_name>-kubeconfig

  2. Verify if the kubeconfig is valid:

    CODE 
    kubectl get namespaces -A --kubeconfig <cluster_name>-kubeconfig

  3. Verify the output of the previous command:

No errors in the output

If your output shows no errors, the error message is not related to a kubeconfig.

Error in the output

If the output shows an error, delete the KommanderCluster object via CLI:

CODE 
kubectl delete kommandercluster -n <WORKSPACE_NAMESPACE> <WRONG_KOMMANDER_CLUSTER>

(info) At this particular stage and in the context of converting your cluster, deleting your KommanderCluster will not affect your environment. However, DO NOT delete your KommanderCluster in other scenarios, as it detaches the referenced cluster from the Management cluster.

Finally, restart the cluster conversion process with the UI or CLI.

Essential cluster has more than one instance of v1beta1/clusters.cluster.x-k8s.io

D2iQ does not support converting Essential clusters that contain the Cluster API resources of more than one cluster.

Ensure your Essential cluster only contains its own CAPI resources and does not contain the CAPI resources of other clusters.

Next Topic:

Restore your Backup and Retry the Cluster Expansion

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close