Skip to main content
This topic describes how to upgrade Kubernetes in your Google Kubernetes Engine (GKE) Domino deployment. GKE is hosted on Google Cloud Platform (GCP).
Immediately after the Kubernetes upgrade, you must upgrade Domino to a compatible version of Kubernetes. Domino does not work as expected until this is completed.For example, after upgrading Kubernetes to 1.22, you must upgrade to Domino 5.2 or later. Kubernetes 1.22 is not compatible with older versions of Domino. Similarly, after upgrading to Kubernetes 1.23 or 1.24, you must upgrade to Domino 5.3 or later.

Prerequisites

To upgrade Kubernetes in GKE, you must have a Unix or Linux terminal with the following: Use environment variables to set the values of IDs, names, and labels. This simplifies the commands you’ll run while upgrading:

Get cluster credentials

  1. If you aren’t already signed in with gcloud, run gcloud init.
  2. To protect your current configuration file from being overwritten, run export KUBECONFIG=$(pwd)/kubeconfig.
  3. Get the remote kubeconfig:

Disable the disruption budgets

You must temporarily disable the PodDisruptionBudget (PDB) for certain services. To do this, back up the PDBs, delete the original PDBs, then update Kubernetes and restore the PDBs from the backup after the update is complete.
  1. Back up the PDBs:
  2. Delete the PDBs:

Determine the upgrade version

  1. Get the available GKE versions:
  2. Get the current master version:
You can only upgrade by one minor version at a time. For example, if you are on Kubernetes version 1.22, you can upgrade to version 1.23.

Update the cluster

  1. Upgrade the control plane. This might take several minutes to complete. Monitor the GCP console for the status of the cluster upgrade.
  2. Upgrade the node pools:

Restore the disruption budgets

Run these commands from the same folder as the backup:
Last modified on August 6, 2026