How deeply does Google Anthos in Action cover software upgrade?

Explains configuration edits, tool selection, sequencing, prechecks, compatibility risks, and parallel-cluster rollback planning.

Software upgrade

As explained in Google Anthos in Action

Cluster upgrading is the process of changing a cluster's software or platform components to a newer version.

Cluster upgrading changes Anthos cluster software or platform components to newer versions. In nonstandalone Anthos on bare metal installations, upgrade the admin or hybrid cluster before its user clusters. section 5.2.1 section 17.5

A practical upgrade sequence is:

Review compatibility and run available prechecks before changing the cluster. section 5.2.1
Modify the cluster configuration to replace the existing Anthos version with the target version. section 17.5.1 section 17.5.2
Download the matching bmctl version and run bmctl upgrade cluster against the cluster name and administrative kubeconfig. section 17.5.1 section 17.5.2
Upgrade user clusters only after the admin or hybrid cluster has completed successfully. section 17.5 section 17.5.2

Reducing production upgrade risk

Keep spare hardware for a parallel new cluster, move workloads from the old cluster, and place a load balancer before both clusters so traffic can shift back if the upgrade fails. section 5.2.1

apiVersion: baremetal.cluster.gke.io/v1
kind: Cluster
metadata:
name: admin-cluster
namespace: cluster-admin-cluster
spec:
type: hybrid
# Anthos cluster version.
anthosBareMetalVersion: 1.13.0

A cluster configuration declares the target Anthos on bare metal version before the upgrade command runs. section 17.5.1

How Google Anthos in Action covers it

liveBook manning.com

Read Google Anthos in Action on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

PostgreSQL Mistakes and How to Avoid ThemA software upgrade is the process of installing a newer version of software or its supporting components.
liveBook manning.com

Infrastructure as Code, Patterns and Practices: With examples in Python and TerraformA tool upgrade is the process of replacing an infrastructure tool with a newer version while preserving or adapting its managed resources and configuration.
liveBook manning.com

Kafka for ArchitectsAn upgrade is a change that replaces software or its components with a newer version to improve security, stability, functionality, or compatibility.
liveBook manning.com

MongoDB 8.0 in Action, Third EditionAn upgrade is a change that moves a software system or database deployment to a newer version.

Compare how 5 books explain software upgrade →

Related concepts

pg_upgradeimplemented by · pg_upgrade is a PostgreSQL utility that upgrades a database cluster to a newer major version while preserving its data.
bmctluses · bmctl is a command-line tool and binary executable for deploying and managing Anthos clusters on bare-metal infrastructure.
release notesuses · Release notes are documentation summarizing changes, fixes, features, compatibility considerations, and other notable information associated with a software release.
major upgradeincludes · A major upgrade is a software-version upgrade that introduces substantial changes and typically requires explicit initiation and preparation.
rolling updateuses · A rolling update is a deployment or upgrade technique that updates or replaces instances or resources incrementally rather than all at once, allowing the rest of the system to continue operating during the change.

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.