Skip to main content
Skip table of contents

Post Conversion Cleanup: Clusters run on Different Cloud Platforms

For a DKP Enterprise Management cluster to manage a cluster hosted in another cloud provider, you must ensure the Management cluster has all the necessary permissions.


Prior to running these commands, you must ensure that the DKP Management Enterprise cluster is configured with the necessary platform specific permissions to manage the incoming CAPI objects that backs the infrastructure resources in the target cloud platform.

For example, for the DKP Enterprise Managed cluster to manage CAPI clusters in AWS, refer to

DKP supports expanding your platform in the following scenarios:

DKP Enterprise Management cluster host provider

DKP Enterprise Management cluster IAM permissions

DKP Essential cluster host provider


AWS, GCP, vSphere, Pre-provisioned


AWS, GCP, vSphere, Pre-provisioned


AWS, GCP, vSphere, Pre-provisioned





AWS, GCP, vSphere, Pre-provisioned

Moving the CAPI Resources

  1. Following the conversion into a DKP Enterprise managed cluster, run the following command to move the CAPI Objects:

    dkp move capi-resources --from-kubeconfig <essential_cluster_kubeconfig> --to-kubeconfig <enterprise_cluster_kubeconfig> --to-namespace ${WORKSPACE_NAMESPACE}
  2. Verify that the output looks similar to the following:

    ✓ Moving cluster resources 
    You can now view resources in the moved cluster by using the --kubeconfig flag with kubectl. For example: kubectl --kubeconfig=<enterprise_cluster_kubeconfig> get nodes
  3. After moving the resources, run the following command to remove the CAPI controller manager deployments:

    dkp delete capi-components --kubeconfig <essential_cluster_kubeconfig>

Next Step


JavaScript errors detected

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

If this problem persists, please contact our support.