Install Continuous Delivery for PE

The Continuous Delivery for PE installation process creates a Kubernetes cluster for you and installs the application on the cluster.

Before you begin

Note: Installing Continuous Delivery for PE by using an existing instance of the platform admin console (such as the one created when installing Puppet Comply) is not currently supported. Follow the instructions on this page to create a dedicated Continuous Delivery for PE instance of the platform admin console.

Review the system requirements.

While Continuous Delivery for PE can be installed on a single server, installing on three servers is recommended to provide redundancy. Each server must meet the following minimum requirements:


Memory	Storage	CPUs	Open ports
16 GB	At least 200 GB for `/opt/replicated` At least 32 GB for `/var/lib/kubelet` At least 40 GB for `/var/lib/containerd` Note: If you first installed the platform admin console prior to 7 December 2020, you can safely continue to allocate 40 GB of storage to `/var/lib/docker` instead.	8 (or equivalent)	TCP: 443, 2379,2380, 6443, 6783, 8000, 8800, and 10250 UDP: 6783 and 6784

Note: If Continuous Delivery for PE is used by more than one team in your organization, allocate additional storage space to /opt/replicated to support the increased load on the system.

Note: Swap, Firewalld, and SELinux are not supported for use with this version of Continuous Delivery for PE. The installation script will attempt to disable these services if they are present.

Ensure that IP address ranges 10.96.0.0/22 and 10.32.0.0/22 are locally accessible. See Resolving IP address range conflicts for instructions.

This installation process results in a basic Continuous Delivery for PE instance that is configured for optional high availability. Installation takes several (mostly hands-off) minutes to complete, so get yourself a snack to enjoy during the process.

Create a DNS entry for the Continuous Delivery for PE service. This entry is separate from the DNS entry for the host Continuous Delivery for PE is installed on.
If you decide to use a high availability architecture for your installation, this DNS entry will be pointed at a load balancer. Once installation is complete, we'll walk you through the optional process of setting up the load balancer and adding additional control plane nodes to enable high availability.
From the command line of your primary (control plane) node, run the installation script:
```
curl -sSL https://pup.pt/install-cd4pe | sudo bash -s ha
```
1. When prompted for a load balancer address, enter the address of the DNS entry for the Continuous Delivery for PE service that you created in step 1.
2. When the installation script prints the platform admin console address and password, make a careful note of these credentials:
```
---
Kotsadm: http://<PLATFORM ADMIN CONSOLE ADDRESS>:8800
Login with password (will not be shown again): <PASSWORD>
---
```
  Note: If you lose this password or wish to change it, see Resetting the platform admin console password for instructions.
3. When the installation script is complete, run bash -l to reload the shell.
Tip: If the installation script fails, run the following and upload the results to the Puppet Support team:
```
kubectl support-bundle https://kots.io
```
If you're installing as the root user, run the command directly:
```
/usr/local/bin/kubectl-support_bundle https://kots.io
```
Navigate to the platform admin console using the address provided by the installation script and follow the prompts.
The platform admin console is where you manage the Continuous Delivery for PE application. You’ll be guided through the process of setting up SSL certificates, uploading a license, and checking to make sure your infrastructure meets Continuous Delivery for PE system requirements.
To configure your installation click Config.
1. In the Hostname field, enter the name of the DNS entry for the Continuous Delivery for PE service that you created in step 1.
2. Set up the Continuous Delivery for PE root user account: enter an email address and choose a password.
3. Configure any other settings on the page relevant to your installation, such as external databases, customized endpoints, or TLS certificates.
4. When you've finished making any necessary changes to the configuration, click Save config. Saving your new configuration settings prompts the creation of a new Continuous Delivery for PE version.
Click Go to new version, which redirects you to the Version history tab. The newly created version is shown in the All versions section of the page.
Monitor the new version's preflight checks. The Running Checks indicator is shown on the screen while your system is checked to make sure your cluster meets minimum system requirements. When the preflight check is 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.
Once the version is ready to deploy, click Deploy. On the Application tab, monitor the application for readiness.
The application's status is shown as Missing for several minutes while deployment is underway. To monitor the deployment's progress, run kubectl get pods --watch.
When the deployment is complete, the application status changes to Ready.
Installation is now complete! Navigate to https://<HOSTNAME> (using the name of the DNS entry you created in step 1 and entered on the Config screen in step 4a) 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.
To make sure your new installation is highly dependable and fault-tolerant, follow the instructions in Enable high availability.

Install Continuous Delivery for PE

Sections