Version 1.9. This is the most recent version. It's supported as outlined in the Anthos version support policy, offering the latest patches and updates for security vulnerabilities, exposures, and issues impacting Anthos clusters on bare metal. For release details, see the release notes 1.9. For a complete list of each minor and patch release in chronological order, see the combined release notes.

Available supported versions: 1.9  |   1.8  |   1.7  |  

Recover a failed upgrade in Anthos clusters on bare metal

Occasionally, Anthos clusters on bare metal 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.

Recover user cluster upgrades

User clusters are upgraded from an associated admin cluster with the kubectl apply 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.