Instructions on how you can convert an Essential Cluster to a Managed cluster with no Networking Restrictions with the DKP UI.

Ingress that contains Traefik-Forward-Authentication configuration will be not available during the expansion process, therefore, your DKP Essential cluster will not be accessible externally for several minutes. Access from within the cluster via Kubernetes service hostname (for example, http://SERVICE_NAME.NAMESPACE:PORT) is not affected.

See Downtime Considerations for more information.

How to attach an existing cluster that has no additional networking restrictions

Use this option when you want to attach a cluster that does not require additional access information.

  1. From the top menu bar, select your target workspace.

  2. On the Dashboard page, select the Add Cluster option in the Actions dropdown menu at the top right.

  3. Select Attach Cluster.

  4. Select the No additional networking restrictions card. Alternatively, if you MUST use network restrictions, stop following the steps below, and see the instructions on the page Attach a Cluster with Network Restrictions.

  5. In the Cluster Configuration section, paste your kubeconfig file into the field, or select the Upload kubeconfig File button to specify the file.

  6. The Cluster Name field will automatically populate with the name of the cluster is in the kubeconfig. You can edit this field with the name you want for your cluster.

  7. The Context select list is populated from the kubeconfig. Select the desired context with admin privileges from the Context select list.

  8. Add labels to classify your cluster as needed.

  9. Select Create to attach your cluster.

Verify the Conversion

Run the following commands in the Management cluster. For general guidelines on how to set the context, refer to Provide Context for Commands with a kubeconfig File.

  1. To verify that the conversion is successful, check the KommanderCluster object:

    kubectl wait --for=condition=AttachmentCompleted kommandercluster <cluster name> -n ${WORKSPACE_NAMESPACE} --timeout 30m
    CODE

  2. The following output appears if the conversion is successful:

    kommandercluster.kommander.mesosphere.io/<cluster name> condition met
    CODE

After conversion, all Platform Applications will be in the Kommander Namespace in the Managed Cluster.

Next Steps

Post Conversion Cleanup: Cluster Autoscaler Configuration

See Also

Troubleshooting