Preparing for PPC deployment

The PCT is a pre-packaged deployment archive. It contains the infrastructure-as-code scripts, Helm charts, and bootstrap tooling. These are required to provision a PPC on your target cloud platform. It automates the creation of the Kubernetes cluster, networking, identity configuration, and installation of Protegrity microservices. Download and extract the PCT on your jump box before starting the deployment process.

Note: If there is an existing cluster from a previous install, clean up your local registry on the jump box. Also clean up any existing clusters by running ./bootstrap.sh --cloud azure destroy from /deployment before proceeding.

During installation, the system may prompt for the system password and require sign-in to Microsoft Azure. If the Azure CLI is not already logged in, the bootstrap script automatically runs az login --use-device-code. A device-code prompt similar to the following appears.

[YYYY-MM-DD HH:MM:SS] Azure CLI not logged in. Triggering az login...
To sign in, use a web browser to open the page https://login.microsoft.com/device and enter the code XXXXXXXX to authenticate.

To sign-in to Microsoft Azure, perform the following steps:

1. Open the displayed URL in a browser, and enter the code shown in the terminal.
2. Complete the SSO sign-in and follow the on-screen instructions.
3. After successful authentication, the script continues automatically.

To download and extract PCT, perform the following steps:

1. Log in to the My.Protegrity portal.

2. Navigate to Product Management > Explore Products > AI Team Edition > Platform Installation.

3. From the Actions column for Protegrity Provisioned Cluster, click the Download Product icon. This downloads the PPC 1.2 archive.

4. Create a deployment_120 directory on the jumpbox.

   mkdir deployment_120 && cd deployment_120
   

5. Copy the PCT to the deployment_120 directory on the jump box.

6. Extract the PCT.

   tar -xvf PPC-K8S-ALL_1.2.0.x.tar
   

   Note: For more information about the PCT, refer to My.Protegrity or the release notes.