Configure and deploy Continuous Delivery for PE in an offline environment

Use these instructions to install Continuous Delivery for Puppet Enterprise (PE) in an air-gapped or offline environment where the Continuous Delivery for PE host server does not have direct access to the internet.

Before you begin
Install Puppet Application Manager (PAM).
  1. In PAM, upload your Continuous Delivery for PE license and follow the prompts to set up SSL certificates and make sure your infrastructure meets Continuous Delivery for PE system requirements.
  2. When prompted, upload an .airgap bundle for the most recent version of Continuous Delivery for PE. These are the available bundles:
    Version Release date Airgap bundle
    4.15.1 14 June 2022 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.15.1.airgap
    4.15.0 7 June 2022 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.15.0.airgap
    4.14.0 5 May 2022 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.14.0.airgap
    4.13.0 5 April 2022 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.13.0.airgap
    4.12.1 7 March 2022 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.12.1.airgap
    4.12.0 2 March 2022 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.12.0.airgap
    4.11.5 22 February 2022 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.11.5.airgap
    4.11.4 14 February 2022 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.11.4.airgap
    4.11.2 2 February 2022 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.11.2.airgap
    4.11.1 20 January 2022 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.11.1.airgap
    4.11.0 20 January 2022 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.11.0.airgap
    4.10.5 20 December 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.10.5.airgap
    4.10.4 17 December 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.10.4.airgap
    4.10.3 10 December 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.10.3.airgap
    4.10.2 9 December 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.10.2.airgap
    4.10.1 11 November 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.10.1.airgap
    4.10.0 9 November 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.10.0.airgap
    4.9.0 8 September 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.9.0.airgap
    4.8.2 31 August 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.8.2.airgap
    4.8.1 24 August 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.8.1.airgap
    4.8.0 10 August 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.8.0.airgap
    4.7.2 26 July 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.7.2.airgap
    4.7.1 12 July 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.7.1.airgap
    4.7.0 8 July 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.7.0.airgap
    4.6.1 16 June 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.6.1.airgap
    4.6.0 3 June 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.6.0.airgap
    4.5.2 11 May 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.5.2.airgap
    4.5.1 27 April 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.5.1.airgap
    4.5.0 22 April 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.5.0.airgap
    4.4.2 13 April 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.4.2.airgap
    4.4.1 29 March 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.4.1.airgap
    4.4.0 11 March 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.4.0.airgap
    4.3.3 23 February 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.3.3.airgap
    4.3.2 3 February 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.3.2.airgap
    4.3.1 26 January 2021 https://cd4pe-builds.s3.amazonaws.com/stable/cd4pe-4.3.1.airgap
    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
  3. To configure your Continuous Delivery for PE installation, click Config, and:
    1. Enter a hostname for the Continuous Delivery for PE installation.
    2. Set a password for the Continuous Delivery for PE root user account.
    3. Select where to host the webhook (for source control integration) and local container registry (in Puppet-supported offline installs) endpoints.
      • Use a Nodeport: All Kubernetes hosts listen on this NodePort and forward traffic to the appropriate endpoint.
      • Use an Ingress with a hostname: The endpoint listens on ports 80 (HTTP) and 443 (HTTPS) for requests using the specified hostname.
    4. Configure any other settings on the page relevant to your installation, such as external databases, customized endpoints, a load balancer, or TLS certificates.
    5. When you've finished editing the configuration, click Save config. Saving new configuration settings initiates creation of a new Continuous Delivery for PE version.
  4. Click Go to new version, which redirects you to the Version history tab, and locate the new version in the All versions section of the page.
  5. Monitor the new version's preflight checks. The Running Checks indicator is visible while Continuous Delivery for PE checks your system to make sure your cluster meets minimum system requirements. When the preflight checks are complete:
    • If the status is Checks Failed, click View preflights, correct the issues, and click Re-run. Repeat this step as needed.
      Important: Do not move on until all preflight checks pass.
    • If the status is Ready to Deploy, move on to the next step.
  6. Once the version is ready to deploy, click Deploy and monitor the application's status on the Application tab.
    During deployment, the application is in Missing status for several minutes. You can run kubectl get pods --watch to monitor the deployment's progress.

    When deployment is complete, the application's status changes to Ready.

  7. Navigate to https://<HOSTNAME> (using the hostname you entered on the Config screen) and sign into Continuous Delivery for PE.
What to do next

If you're upgrading to the 4.x series from a version in the 3.x series, see Migrating 3.x data to 4.x.

If you're new to Continuous Delivery for PE, see Getting started with Continuous Delivery for PE to learn about the software's core features and workflows.