Production configuration
Review and override these settings before deploying to production for high availability, data safety, and security compliance.
By default, the PCT is configured to deploy a FIPS-enabled cluster using FIPS-compliant node OS images.
Non-FIPS deployment: Before proceeding with the installation, complete the steps in Configuring PPC for Non-FIPS Deployment on Microsoft Azure to modify the required Terraform configuration files. Then proceed with either the automated or component-based installation below.
FIPS deployment: No additional configuration is required. Proceed directly with either the automated or component-based installation below.
The PPC cluster can be deployed using one of the following methods:
Automated script-based installation: This method requires the bootstrap.sh script to deploy the PPC cluster. The script installs the required software and dependencies, prompts to provide the required information, and deploys the cluster automatically.
Manual component-based installation: This method requires to perform the deployment of each component to install the PPC cluster. The configuration files are edited to provide the required information and then deploy the cluster.
Note: A PPC can be deployed in regions where minimum two zones are present.
Review and override these settings before deploying to production for high availability, data safety, and security compliance.
Complete the steps provided in this section to configure the Protegrity Cluster Template (PCT) for a non-FIPS PPC deployment on Azure AKS.
Complete the steps provided in this section to deploy PPC in Microsoft Azure AKS.
Complete the steps provided in this section to update the configuration files and deploy PPC in Microsoft Azure AKS.
Was this page helpful?