Prerequisites

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

Jump box

PPC is deployed and managed from a dedicated EC2 instance, referred to as the jump box.

A newly provisioned EC2 instance must be used as the jump box for PPC deployment.
The jump box must be provisioned in the same AWS region where the PPC cluster is deployed. This ensures proper connectivity and access to regional resources.
Supported operating systems: RHEL 10, Debian 12, or Debian 13.

Note: Ensure to retain the original jump box used for installation. A snapshot of the jump box must be maintained to prevent data loss.

Preparing for PPC deployment

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

If the jump box is already set previously, run the ./bootstrap.sh --cloud aws destroy command in the directory where the cluster is installed. This ensures that the local registry on the jump box and the clusters are cleaned up before proceeding with a new installation.

Warning: Do not install or manage multiple clusters from the same working directory. Each cluster deployment maintains its own Terraform/OpenTofu state, and reusing a directory can overwrite state files, causing loss of cluster tracking and unintended cleanup behavior.
Use a dedicated directory, and jump box, where possible, per cluster, and always verify the active kubectl context before running cleanup commands such as ./bootstrap.sh --cloud aws destroy.

Installation on

Prerequisites

Jump box

Preparing for PPC deployment