Make the New GCP Cluster Self-Managed

DKP deploys all cluster lifecycle services to a bootstrap cluster, which then deploys a workload cluster. When the workload cluster is ready, move the cluster lifecycle services to the workload cluster, which makes the workload cluster self-managed. This section describes how to make a workload cluster self-managed.

Before starting, ensure you create a workload cluster as described in Create a New GCP Cluster.

This page contains instructions on how to make your cluster self-managed. This is necessary if there is only one cluster in your environment, or if this cluster should become the Management cluster in a multi-cluster environment.

If you already have a self-managed or Management cluster in your environment, skip this page.

Make the new Kubernetes cluster manage itself

Follow these steps:

Deploy cluster lifecycle services on the workload cluster:

dkp create capi-components --kubeconfig ${CLUSTER_NAME}.conf

CODE

✓ Initializing new CAPI components

CODE

Move the Cluster API objects from the bootstrap to the workload cluster:
The cluster lifecycle services on the workload cluster are ready, but the workload cluster configuration is on the bootstrap cluster. The move command moves the configuration, which takes the form of Cluster API Custom Resource objects, from the bootstrap to the workload cluster. This process is also called a Pivot.
```
dkp move capi-resources --to-kubeconfig ${CLUSTER_NAME}.conf
```
CODE
```
✓ Moving cluster resources
You can now view resources in the moved cluster by using the --kubeconfig flag with kubectl. For example: kubectl --kubeconfig=gcp-example.conf get nodes
```
CODE
NOTE: To ensure only one set of cluster lifecycle services manages the workload cluster, DKP first pauses reconciliation of the objects on the bootstrap cluster, then creates the objects on the workload cluster. As DKP copies the objects, the cluster lifecycle services on the workload cluster reconcile the objects. The workload cluster becomes self-managed after DKP creates all the objects. If it fails, the move command can be safely retried.

Wait for the cluster control-plane to be ready:

kubectl --kubeconfig ${CLUSTER_NAME}.conf wait --for=condition=ControlPlaneReady "clusters/${CLUSTER_NAME}" --timeout=20m

CODE

cluster.cluster.x-k8s.io/gcp-example condition met

CODE

Use the cluster lifecycle services on the workload cluster to check the workload cluster status:

NOTE: After moving the cluster lifecycle services to the workload cluster, remember to use DKP with the workload cluster kubeconfig.

dkp describe cluster --kubeconfig ${CLUSTER_NAME}.conf -c ${CLUSTER_NAME}

CODE

NAME                                                                      READY  SEVERITY  REASON  SINCE  MESSAGE
Cluster/gcp-example                                                       True                     14s
├─ClusterInfrastructure - GCPCluster/gcp-example
├─ControlPlane - KubeadmControlPlane/gcp-example-control-plane            True                     14s
│ ├─Machine/gcp-example-control-plane-6fbzn                               True                     17s
│ │ └─MachineInfrastructure - GCPMachine/gcp-example-control-plane-62g6s
│ ├─Machine/gcp-example-control-plane-jf6s2                               True                     17s
│ │ └─MachineInfrastructure - GCPMachine/gcp-example-control-plane-bsr2z
│ └─Machine/gcp-example-control-plane-mnbfs                               True                     17s
│   └─MachineInfrastructure - GCPMachine/gcp-example-control-plane-s8xsx
└─Workers
  └─MachineDeployment/gcp-example-md-0                                    True                     17s
    ├─Machine/gcp-example-md-0-68b86fddb8-8glsw                           True                     17s
    │ └─MachineInfrastructure - GCPMachine/gcp-example-md-0-zls8d
    ├─Machine/gcp-example-md-0-68b86fddb8-bvbm7                           True                     17s
    │ └─MachineInfrastructure - GCPMachine/gcp-example-md-0-5zcvc
    ├─Machine/gcp-example-md-0-68b86fddb8-k9499                           True                     17s
    │ └─MachineInfrastructure - GCPMachine/gcp-example-md-0-k8h5p
    └─Machine/gcp-example-md-0-68b86fddb8-l6vfb                           True                     17s
      └─MachineInfrastructure - GCPMachine/gcp-example-md-0-9h5vn

CODE

Remove the bootstrap cluster, as the workload cluster is now self-managed:

dkp delete bootstrap --kubeconfig $HOME/.kube/config
✓ Deleting bootstrap cluster

CODE

Known Limitations

DKP only supports moving all namespaces in the cluster; DKP does not support migration of individual namespaces.