Skip to main content
Skip table of contents

Upgrade Cluster Node Pools

Upgrading a node pool involves draining the existing nodes in the node pool and replacing them with new nodes. In order to ensure minimum downtime and maintain high availability of the critical application workloads during the upgrade process, we recommend deploying Pod Disruption Budget (Disruptions) for your critical applications.

The Pod Disruption Budget will prevent any impact on critical applications as a result of misconfiguration or failures during the upgrade process. 



  1. Deploy Pod Disruption Budget for your critical applications. If your application can tolerate only one replica to be unavailable at a time, then you can set Pod disruption budget as shown in the following example. The example below is for NVIDIA GPU node pools, but the process is the same for all node pools. 

Repeat this step for each additional node pool.

Create the file: pod-disruption-budget-nvidia.yaml

apiVersion: policy/v1
kind: PodDisruptionBudget
  name: nvidia-critical-app
  maxUnavailable: 1
      app: nvidia-critical-app

 Apply the YAML file above using the following command:

kubectl create -f pod-disruption-budget-nvidia.yaml


2. Prepare OS image for your node pool using Konvoy Image Builder.

Related Topics:

Enterprise: Upgrade the Management Cluster Kubernetes Version

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.