Deploying PPC on

Automated script-based installation

Mon, 01 Jan 0001 00:00:00 +0000

Before you begin

Before running the bootstrap 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.

The repository provides a bootstrap script that automatically installs or updates the following software on the jump box:

AWS CLI - Required to communicate with the AWS account.
OpenTofu - Required to manage infrastructure as code.
kubectl - Required to communicate with the Kubernetes cluster.
Helm - Required to manage Kubernetes packages.
skopeo - Required to copy and inspect container images across registries without requiring a daemon.
jq - Required to parse JSON.

The bootstrap script also checks if you have the required permissions on AWS. It then sets up the EKS cluster and installs the microservices required for deploying the PPC.

Manual component-based installation

Mon, 01 Jan 0001 00:00:00 +0000

This section is intended for enterprise customers who need full control over each stage of the EKS cluster deployment. Use this path when infrastructure stages must be reviewed or approved separately. Use it also when integration with an existing CI/CD pipeline is required. Use it when corporate change-management controls prevent running an all-in-one automated script. All stages must be performed from the same jump box.

Review the Deploying PPC overview and AWS prerequisites before running tofu apply.

In-cluster deployment

Mon, 01 Jan 0001 00:00:00 +0000

This section is intended for users who already have an EKS cluster provisioned and managed outside of the PPC installer. In a standard PPC installation, the installer provisions the EKS cluster and the required AWS resources. In an in-cluster deployment, however, the user creates the cluster. It already exists before the PPC installation begins. Cluster information must be provided to deploy PPC onto the existing EKS cluster. Unlike the automated script-based installation or the manual component-based installation, the installer does not create these AWS resources. They must already exist before you begin.