Upgrading the PPC

Before you begin

Before starting an upgrade, ensure the following conditions are met:

• Access to the jump box associated with the PPC v1.0.0 cluster is required. This must be the same jump box used during the PPC v1.0.0 installation.

• Ensure that the correct cluster is set before performing the upgrade operation, using the following command.

  kubectl config current-context
  

Note: Before running the bootstrap or resiliency scripts as the root user on RHEL, ensure that /usr/local/bin, and the AWS CLI binary path, if applicable, is included in the $PATH. Alternatively, run the script using a non-root user, such as ec2-user where /usr/local/bin is already part of the default $PATH.

To upgrade the PPC, perform the following steps:

1. Create a new directory on the jump box using the following command.

   mkdir <new_directory> && cd <new_directory>
   

2. Download the upgrade archive to the new directory.

3. Extract the archive contents using the following command.

   tar -xvf PPC-K8S-64_x86-64_AWS-EKS_1.0.1.66.tar
   

4. Initiate upgrade using the following command.

   ./bootstrap.sh --upgrade --directory-path <path to archive of v1.0 cluster>
   

   where path to archive of v1.0 cluster corresponds to the location of the archive of PPC v1.0. This path is required to access the terraform state file.

After the upgrade is successful, PCF upgrade completed successfully. message is displayed.

Note: The cluster upgrade process can take 10-15 minutes approximately and it may differ accordingly.

Post Upgrade Steps

Verify all nodes are Ready

Run the following command, to verify if all nodes are ready.

kubectl get nodes -o wide

Verify all pods are Running

Run the following command, to verify if all pods are running.

kubectl get pods -A

Verify Helm releases

Run the following command, verify if the helm releases are in “deployed” state.

helm list -A

Recovering from a Failed Upgrade

If the session is terminated during upgrade due to network issues, power outage, or any such issues, then the upgrade process stops. To restart the process, perform the following steps:

1. Restore to the previous stable version of PPC.
   For more information about restoring the PPC, refer to the Restoring the PPC.

2. Upgrade the PPC to v1.0.1.

3. Delete the original PPC v1.0.0 cluster where the upgrade operation had failed, using the following command.

   # Navigate to setup directory 
   cd iac_setup
   
   # Clean up all resources
   make clean
   

Warning: Do not install or manage multiple clusters from the same working directory. Each cluster deployment maintains its own Terraform/OpenTofu state, and reusing a directory can overwrite state files, causing loss of cluster tracking and unintended cleanup behavior.
Use a dedicated directory, and jump box, where possible, per cluster, and always verify the active kubectl context before running cleanup commands such as make clean.
To check the active kubectl context, run the following command:
kubectl config current-context