New versions of Continuous Delivery for Puppet Enterprise (PE) are released regularly. Upgrading to the current version ensures you're always taking advantage of the latest features, fixes, and improvements.
These are the valid upgrade paths for Continuous Delivery for PE.
|If you're on version...||Upgrade to version...||Notes|
|4.x||You're up to date!|
|3.13.x||4.x||You must upgrade to version 3.13.x in order to access the 3.x to 4.x data migration tool.|
|3.12.x or earlier||3.13.x|
Upgrade Continuous Delivery for PE
Check for, download, and deploy updates from the Version history tab in the platform admin console. These instructions apply to installations in online environments.
- In the platform admin console, click Version history.
Click Check for updates.
Configure an automatic update check by clicking Configure automatic updates. You can check for updates hourly, every four hours, daily, weekly, or at a custom interval.
- If an update is available, the platform admin console downloads it for you and performs preflight checks on your system to make sure your cluster meets system requirements for the new version. Review the outcome of these checks by clicking View preflight.
- When you're ready to upgrade to the new version of Continuous Delivery for PE, click Deploy.
Upgrade the platform admin console
Upgrade the platform admin console to take advantage of new features and bug fixes, and to upgrade your cluster to the latest version of Kubernetes when one is available.
On your control plane node, rerun the installation script, passing in any
arguments you included when installing for the first time:
curl -sSL https://pup.pt/install-cd4pe | sudo bash
If a new version of Kubernetes is available, the
system will provide upgrade scripts to run on each node in your cluster.
Node draining is performed as part of a Kubernetes upgrade. The node draining process can take several minutes to complete.Note: During the Kubernetes upgrade process, nodes are not able to properly route network connections. Make sure you have load balancers or a multi-node failover process in place, or schedule downtime before upgrading.
Upgrade in an offline environment
Users operating in environments without direct access to the internet must use the links below to upgrade to the latest version of Continuous Delivery for PE or the platform admin console.
To upgrade Continuous Delivery for PE: Download the latest
version's airgap bundle from the chart below.
Version Release date Airgap bundle 4.2.4 17 December 2020 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.2.4.airgap 4.2.3 17 November 2020 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.2.3.airgap 4.2.2 12 November 2020 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.2.2.airgap 4.2.1 5 November 2020 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.2.1.airgap 4.2.0 3 November 2020 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.2.0.airgap 4.1.3 15 October 2020 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.1.3.airgap 4.1.2 8 October 2020 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.1.2.airgap 4.1.1 29 September 2020 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.1.1.airgap 4.0.1 14 September 2020 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.0.1.airgap 4.0.0 25 August 2020 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.0.0.airgap
To upgrade the platform admin console:
From a workstation with internet access, download the latest version of
the cluster installation bundle (note that this bundle is ~3GB):
Copy the installation bundle to your primary Continuous Delivery for PE server and unpack it:
tar xzf cd4pe-bundle
Run the installation command:
cat install.sh | sudo bash -s airgap
- From a workstation with internet access, download the latest version of the cluster installation bundle (note that this bundle is ~3GB):
Upgrade an automated installation
If you installed Continuous Delivery for PE following the automated installation instructions, run a script to upgrade to the latest version.
From the command line of your primary (control plane) node, run the upgrade
kubectl kots upstream upgrade cd4pe --namespace default --deploy
- Wait five minutes to allow the software time to process the change.
http://<NODE IP ADDRESS>:8800and log in with the platform admin console password.If pre-flight checks have passed, the upgraded application is deployed and in the process of starting up. To monitor the deployment's progress, run
kubectl get pods --watch.