Version 1.16. This version is no longer supported. For information about how to upgrade to version 1.28, see Upgrade clusters in the latest documentation. For more information about supported and unsupported versions, see the Versioning page in the latest documentation.
Occasionally, Google Distributed Cloud may run into conditions where you need to
start an upgrade over again, or fix an error condition to complete the upgrade
successfully. The following conditions may occur when upgrading clusters. Try
to complete the cluster upgrade as noted with the condition.
Recover admin, hybrid, and standalone cluster upgrades
Admin, hybrid, and standalone clusters are all upgraded with the bmctl upgrade
command.
If your upgrade doesn't complete successfully, check the following conditions
and try the upgrade again.
bmctl fails to parse the config file due to a mistake. Fix the config file
and rerun the command.
bmctl fails to bootstrap the temporary cluster. Retry the command.
the log files indicate that the upgrade failed a preflight check. Correct the preflight condition, or force
the upgrade.
the upgrade took too long (more than 30 minutes) or timed out. Retry the
upgrade command.
If your upgrade doesn't complete successfully, check the following conditions
and try the upgrade again.
Preflight check failed. Check the preflight check log and fix the
corresponding error.
You may need to construct a new preflight custom resource following these instructions
and apply it to the cluster. Check that the
triggered preflight passes, and that the cluster reconciler
picks up the latest passing state.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[[["Upgrades for admin, hybrid, and standalone clusters are managed using the `bmctl upgrade` command, and if unsuccessful, issues like configuration errors, bootstrap failures, preflight check failures, or timeouts should be addressed."],["User cluster upgrades are initiated from an associated admin cluster via the `kubectl apply` command, and recovery involves checking for preflight check failures and potentially creating a new preflight custom resource."],["Common issues that can occur during upgrades of all clusters include configuration file mistakes, failed bootstrapping, preflight check failures, and timeouts."],["Rerunning commands or making configuration changes based on logged errors or failures are common methods to address upgrade issues."]]],[]]
