<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Deploying PPC on</title><link>https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/azure/installation/deploying_ppc/</link><description>Recent content in Deploying PPC on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/azure/installation/deploying_ppc/index.xml" rel="self" type="application/rss+xml"/><item><title>Automated script-based installation</title><link>https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/azure/installation/deploying_ppc/auto_install/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/azure/installation/deploying_ppc/auto_install/</guid><description>&lt;h2 id="before-you-begin">Before you begin&lt;/h2>
&lt;ul>
&lt;li>
&lt;p>Ensure that all the required resources are in the same resource-group. If the resources are in different resource groups, then ensure to move the resources to the same group before proceeding for PPC deployment.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>The repository provides a bootstrap script that automatically installs or updates the following tools on the jump box:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/cli/azure/">Azure CLI&lt;/a> - Required to communicate with your Microsoft Azure account.&lt;/li>
&lt;li>&lt;a href="https://helm.sh/">Helm&lt;/a> - Required to manage Kubernetes packages.&lt;/li>
&lt;li>&lt;a href="https://github.com/jqlang/jq">jq&lt;/a> - Required to parse JSON.&lt;/li>
&lt;li>&lt;a href="https://kubernetes.io/docs/reference/kubectl/">kubectl&lt;/a> - Required to communicate with the Kubernetes cluster.&lt;/li>
&lt;li>&lt;a href="https://opentofu.org/">OpenTofu&lt;/a> - Required to manage infrastructure as code.&lt;/li>
&lt;li>&lt;a href="https://oras.land/">oras&lt;/a>: Required to pull non‑container, generic OCI artifacts from the registry that are not handled by standard container tooling.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;h3 id="using-a-standard-deployment">Using a Standard Deployment&lt;/h3>
&lt;p>By default, the PCT is configured to deploy a cluster using secure settings. To deploy a standard cluster, the configuration files must be modified accordingly. For the additional configurations, refer to &lt;a href="https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/azure/installation/deploying_ppc/auto_install/#configuring-for-a-standard-deployment">Configuring for a Standard Deployment&lt;/a>.&lt;/p></description></item><item><title>Manual component-based installation</title><link>https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/azure/installation/deploying_ppc/modular_install/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/azure/installation/deploying_ppc/modular_install/</guid><description>&lt;p>This section is intended for enterprise customers who need full control over each stage of the AKS cluster deployment. Use this path when individual infrastructure stages must be reviewed or approved separately. Also use it 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. Each stage is self-contained and can be executed by different teams on the same jump box.&lt;/p></description></item><item><title>In-cluster deployment</title><link>https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/azure/installation/deploying_ppc/in_cluster_deployment/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/azure/installation/deploying_ppc/in_cluster_deployment/</guid><description>&lt;h2 id="setting-up-an-aks-cluster-for-ppc">Setting Up an AKS Cluster for PPC&lt;/h2>
&lt;p>This is the in-cluster deployment guide for Azure. The Azure Kubernetes Service (AKS) cluster and supporting Azure resources are provisioned by the user. The PPC installer then runs only Stage 05 (Helm releases) to deploy the application. The infrastructure is provisioned outside the installer. The cluster must therefore meet the specifications mentioned here.&lt;/p>
&lt;p>Follow the prerequisites below and make sure every item matches how the cluster is created.&lt;/p></description></item></channel></rss>