If you are upgrading a preprovisioned DKP cluster and notice that a node deployment is failing, you may find that the reason is listed as "KIBJobFailedReason".
Solution
You can check the pod logs to find this KIB job in the same namespace as the machines, usually default. In those logs, you may notice an error that resembles the following:
fatal: [123.45.67.89]: FAILED! => {"attempts": 3, "changed": false, "msg": "No package matching 'kubectl-1.21.14-0' found available, installed or updated", "rc": 126, "results": ["No package matching 'kubectl-1.21.14-0' found available, installed or updated"]}
If this is the case, it is usually due to a version mismatch. The version of Kubernetes that you have configured does not match the version that is packaged with this DKP release.
Refer to the release notes or the upgrade docs for this version of DKP to ensure that the Kubernetes version you specify during the update corresponds to the version that is supported by this DKP release.