LATEST VERSION: v1.2 - RELEASE NOTES
Pivotal Container Service v1.2

Upgrading PKS

Page last updated:

This topic explains how to upgrade the Pivotal Container Service (PKS) tile and existing Kubernetes clusters.

For conceptual information about upgrading the PKS tile and PKS-provisioned Kubernetes clusters, see What Happens During PKS Upgrades.

WARNING: Do not manually upgrade your Kubernetes version. The PKS service includes the compatible Kubernetes version.

For information about upgrading PKS on vSphere with NSX-T integration, see Upgrading PKS with NSX-T.

Before You Upgrade

This section describes the activities you must perform before upgrading PKS.

Determine Your Upgrade Path

Use the following table to determine your upgrade path to PKS v1.2.x.

If your current version of PKS is… Then use the following upgrade path:
v1.1.4 or earlier
  1. Upgrade to PKS v1.1.5 or later.
  2. Upgrade to Ops Manager v2.2.2 or later, or Ops Manager v2.3.1 or later.
  3. Upgrade to PKS v1.2.x.
v1.1.5 or later
  1. Upgrade to Ops Manager v2.2.2 or later, or Ops Manager v2.3.1 or later.
  2. Upgrade to PKS v1.2.x.

Prepare to Upgrade

Before you begin upgrading the PKS tile, perform the following steps:

  1. Review the Release Notes for the version or versions of PKS you are upgrading to.

  2. Review What Happens During PKS Upgrades, and consider your workload capacity and uptime requirements.

  3. View your workload resource usage in Dashboard. For more information, see Accessing Dashboard.

    1. If workers are operating too close to their capacity, the PKS upgrade can fail. To prevent workload downtime during a cluster upgrade, Pivotal recommends running your workload on at least three worker VMs, using multiple replicas of your workloads spread across those VMs. For more information, see Maintaining Workload Uptime.
    2. If your clusters are near capacity for your existing infrastructure, Pivotal recommends scaling up your clusters before you upgrade. Scale up your cluster by running pks resize or create a cluster using a larger plan. For more information, see Scaling Existing Clusters.
  4. Verify that your Kubernetes environment is healthy. To verify the health of your Kubernetes environment, see Verifying Deployment Health.

  5. (Optional) Back up the PKS v1.1 control plane. For more information, see Backing Up and Restoring PKS.

During the Upgrade

This section describes the steps required to upgrade to PKS v1.2.x.

Step 1: Upgrade to PKS v1.1.5 or Later

Skip this step if you are already running PKS v1.1.5+.

Follow the procedures detailed in Upgrading PKS in the PKS v1.1 documentation.

Step 2: Upgrade to Ops Manager v2.2.2+ or v2.3.1+

Before you upgrade to PKS v1.2.x, you must upgrade to Ops Manager v2.2.2+ or v2.3.1+.

  1. Follow the procedures detailed in Upgrade Ops Manager and Installed Products to v2.2 or Upgrade Ops Manager and Installed Products to v2.3.

  2. Verify that the PKS control plane remains functional by performing the following steps:

    1. Add more workloads and create an additional cluster. For more information about performing those actions, see About Workload Upgrades in Maintaining Workload Uptime and Creating Clusters.
    2. Monitor the PKS control plane VM by clicking the Pivotal Container Service tile, selecting Status tab, and reviewing the Pivotal Container Service VM’s data points. If any data points are at capacity, scale your deployment accordingly.

Step 3: Upgrade to PKS v1.2.x

To upgrade to PKS v1.2.x, follow the same Ops Manager process that you use to install the tile for the first time.

Your configuration settings migrate to the new version automatically. Follow the steps below to perform an upgrade.

  1. Review the Release Notes for the version you are upgrading to.

  2. Download the desired version of the product from Pivotal Network.

  3. Navigate to the Ops Manager Installation Dashboard and click Import a Product to upload the product file.

  4. Under the Import a Product button, click + next to Pivotal Container Service. This adds the tile to your staging area.

Step 4: Download and Import the Stemcell

PKS v1.2.x uses a Xenial stemcell.

If Ops Manager does not have the Xenial stemcell required for PKS, the PKS tile displays the message Missing stemcell.

Note: If the Stemcell Library in Ops Manager already has a compatible Xenial stemcell, the Missing stemcell link does not appear. You do not need to download or import a new stemcell and can skip this step.

To download and import a new Xenial stemcell, follow the steps below:

  1. On the Pivotal Container Service tile, click on the Missing stemcell link.

    Verify stemcell assignment

  2. In the Stemcell Library, locate Pivotal Container Service and note the required stemcell version.

  3. Visit the Stemcells for PCF (Ubuntu Xenial) page on Pivotal Network, and download the required stemcell version appropriate for your IaaS.

  4. Return to the Installation Dashboard in Ops Manager, and click on Stemcell Library.

  5. On the Stemcell Library page, click Import Stemcell and select the stemcell file you downloaded from Pivotal Network.

  6. Select Pivotal Container Service and click Apply Stemcell to Products.

  7. Verify that Ops Manager successfully applied the stemcell. The stemcell version you imported and applied appears in the Staged column for Pivotal Container Service.

  8. Select the Installation Dashboard link to return to the Installation Dashboard.

Step 5: Verify Errand Configuration

To verify that errands are configured correctly in the PKS tile, perform the following steps.

  1. Click the newly-added Pivotal Container Service tile.

  2. Click Errands.

  3. Under Post-Deploy Errands, verify that the Upgrade all clusters errand is set to Default (On). The errand upgrades a single Kubernetes cluster at a time. Upgrading PKS Kubernetes clusters can temporarily interrupt the service, as described in Service Interruptions.

    WARNING: If you upgrade PKS from v1.1 to v1.2, you must enable Upgrade all clusters errand. This ensures existing clusters can perform resize or delete actions after the upgrade.

  4. Review the other configuration panes. Click Save on any panes where you make changes.

    Note: When you upgrade PKS, you must place singleton jobs in the AZ you selected when you first installed the PKS tile. You cannot move singleton jobs to another AZ.

Step 6: Apply Changes to the PKS Tile

Perform the following steps to complete the upgrade to the PKS tile.

  1. Return to the Installation Dashboard in Ops Manager.

  2. If you are using Ops Manager v2.2, click Review Pending Changes [BETA]. For more information about this Ops Manager page, see Reviewing Pending Product Changes.

  3. If you are using Ops Manager v2.3, click Review Pending Changes. For more information about this Ops Manager page, see Reviewing Pending Product Changes.

  4. Click Apply Changes.

  5. (Optional) To monitor the progress of the Upgrade all clusters errand using the BOSH CLI, do the following:

    1. Log in to the BOSH Director by running bosh -e MY-ENVIRONMENT log-in from a VM that can access your PKS deployment. For more information, see Managing PKS Deployments with BOSH.
    2. Run bosh -e MY-ENVIRONMENT tasks.
    3. Locate the task number for the errand in the # column of the BOSH output.
    4. Run bosh task TASK-NUMBER, replacing TASK-NUMBER with the task number you located in the previous step.

After the Upgrade

After you complete the upgrade to PKS v1.2.x, complete the following verifications and optional upgrades.

Verify the Upgrade

After you apply changes to the PKS tile and the upgrade is complete, perform the following steps:

  1. Verify that your Kubernetes environment is healthy. To verify the health of your Kubernetes environment, see Verifying Deployment Health.

  2. Verify that the PKS control plane remains functional by performing the following steps:

    1. Add more workloads and create an additional cluster. For more information about performing those actions, see About Workload Upgrades in Maintaining Workload Uptime and Creating Clusters.
    2. Monitor the PKS control plane VM by clicking the Pivotal Container Service tile, selecting Status tab, and reviewing the Pivotal Container Service VM’s data points. If any data points are at capacity, scale your deployment accordingly.

(Optional) Upgrade vSphere

If you are deploying PKS on vSphere, consult vSphere Version Requirements, and upgrade vSphere if necessary.


Please send any feedback you have to pks-feedback@pivotal.io.

Create a pull request or raise an issue on the source for this page in GitHub