Version 1.8. This version is no longer supported. For information about how to upgrade to version 1.9, see Upgrading Anthos on bare metal in the 1.9 documentation. For more information about supported and unsupported versions, see the Version history 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 can be reattempted using the `bmctl upgrade` command if they fail due to config file errors, bootstrapping issues, preflight check failures, or timeouts."],["User cluster upgrades, performed via `kubectl apply` from an admin cluster, can be recovered by addressing any preflight check failures."],["If preflight checks fail, the upgrade may require the user to fix the underlying issue, force the upgrade or construct and apply a new preflight custom resource, depending on the cluster type."],["Cluster upgrades that fail due to parsing errors with `bmctl` require the config file to be fixed before the upgrade can be tried again."]]],[]]
