Upon running the command `dkp create cluster` or `kubectl apply/create` (if you have modifications to your cluster settings) you will notice that it will output messages but will not show any progress as to the status of the deployment.
Depending on your nodes performance or internet speed, it will take a considerable amount of time for all the control planes and worker nodes to be deployed.
If you want to check the status, you can first check the machines via the following command:
pogz@Allans-MacBook-Pro konvoy_v2.2.0-rc1 % kubectl get machines
NAME CLUSTER NODENAME PROVIDERID PHASE AGE VERSION
pogz-control-plane-cb92l pogz Provisioning 6s v1.22.8
pogz-md-0-865686686d-5jfnd pogz Pending 10s v1.22.8
pogz-md-0-865686686d-f72wz pogz Pending 10s v1.22.8
pogz-md-0-865686686d-wb9sd pogz Pending 9s v1.22.8
You can further examine whats happening by getting the specific pod in charge of the deployment (it is on the default namespace):
pogz@Allans-MacBook-Pro konvoy_v2.2.0-rc1 % kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
capa-system capa-controller-manager-ddd99cb89-8zl5v 2/2 Running 0 6m29s
capi-kubeadm-bootstrap-system capi-kubeadm-bootstrap-controller-manager-867759cc67-sc8j4 1/1 Running 0 6m42s
capi-kubeadm-control-plane-system capi-kubeadm-control-plane-controller-manager-5df55579c4-bc4fw 1/1 Running 0 6m35s
capi-system capi-controller-manager-79cc58bf5f-zsxhp 1/1 Running 0 6m47s
cappp-system cappp-controller-manager-856b95b44c-l4gj9 1/1 Running 0 6m12s
:
:
default pogz-control-plane-87ff6-provision--1-6r7qm 1/1 Running 0 4m16s
kube-system coredns-78fcd69978-cqdx9 1/1 Running 0 7m48s
kube-system coredns-78fcd69978-j9l5h 1/1 Running 0 7m48s
:
:
From here you can get the logs or use the --follow flag to watch the progress as it completes or errors out.
pogz@Allans-MacBook-Pro konvoy_v2.2.0-rc1 % kubectl logs --follow pogz-control-plane-87ff6-provision--1-6r7qm
2022/03/30 06:07:59 writing new packer configuration to work/provision_build-1648620479-BjxGL
PLAY [Prepare Ansible - Flatcar Python setup] **********************************
TASK [Flatcar no update] *******************************************************
ok: [192.168.245.1]
TASK [exec bootstrap python] ***************************************************
ok: [192.168.245.1]
TASK [check for flatcar python] ************************************************
ok: [192.168.245.1]
TASK [change python if bootstrapped] *******************************************
skipping: [192.168.245.1]
PLAY [Provision] ***************************************************************
TASK [Gathering Facts] *********************************************************
ok: [192.168.245.1]
TASK [include_vars] ************************************************************
ok: [192.168.245.1]
TASK [include_vars] ************************************************************
skipping: [192.168.245.1]
TASK [offline : include_tasks] *************************************************
included: /root/ansible/roles/offline/tasks/upload.yaml for 192.168.245.1
TASK [offline : create images directory] ***************************************
skipping: [192.168.245.1]
:
:
:
TASK [sysprep : Disable Swap] **************************************************
skipping: [192.168.245.1]
TASK [sysprep : Check if firewalld service exists] *****************************
skipping: [192.168.245.1]
TASK [sysprep : Stop and disable firewalld service] ****************************
skipping: [192.168.245.1]
TASK [sysprep : Ensure containterd is started] *********************************
skipping: [192.168.245.1]
TASK [sysprep : Ensure kubelet is started] *************************************
skipping: [192.168.245.1]
RUNNING HANDLER [config : restart containerd] **********************************
ok: [192.168.245.1]
PLAY RECAP *********************************************************************
192.168.245.1 : ok=85 changed=43 unreachable=0 failed=0 skipped=174 rescued=0 ignored=3
If you see an error, you can follow this guide on how to get out of a stuck machine deployment.