Prerequisites

List of prerequisites required to install Protegrity Agent.

The following requirements are met before installing Protegrity Agent v1.2.0 with PPC v1.2.0.

Infrastructure

Protegrity Provisioned Cluster

A PPC cluster is installed and accessible.
For more information, refer to Installing PPC.

Protegrity Traverse and Policy

Ensure that the Protegrity Traverse and Policy Features must be installed.

To verify the Protegrity Traverse is installed, run the following command:

kubectl get pods -n discoverx

To verify the Policy is installed, run the following command:

kubectl get pods -n pty-policy

Tools

Ensure that the following tools are available.

Configuring kubectl

Ensure that the kubectl is configured against the target cluster.

To configure kubectl on AWS, run the following command:

aws eks update-kubeconfig --name <cluster-name> --region us-east-1 --alias <cluster-name>

To configure kubectl on Microsoft Azure, run the following command:

az aks get-credentials --resource-group <resource-group> --name <cluster-name>

Verifying cluster name

Verify that the correct cluster is used before proceeding.

kubectl config current-context

Note (Azure): The PPC AKS clusters are private (*.privatelink.<region>.azmk8s.io). After fetching credentials, confirm the API is reachable using kubectl get ns command.
If the system hangs, then the cluster needs a private network path, such as VPN, jumpbox, or private DNS.

Cloud Vendor ConfigMap

The Helm chart uses the CLOUD_VENDOR key to determine which cloud provider-specific resources are to be deployed.

Ensure that the CLOUD_VENDOR key is present and set to the appropriate value for the target environment, such as aws or azure. If the key is missing or incorrectly configured, the chart may render resources that are not supported by the target platform, causing the installation to fail.

To verify this before installing, run the following command:

kubectl get configmap nfa-config -n default -o jsonpath='{.data.CLOUD_VENDOR}{"\n"}'
  • For Azure, the AKS: value must be "azure".
  • For AWS, the AWS/EKS: value must be "aws" or empty.

The ARCHITECTURE key (amd64 | arm64, default amd64) for' arm64 architecture uses Azure Ampere nodes in Azure and AWS Graviton nodes in AWS.

Supported Models

The Protegrity Agent requires an administrator to configure the underlying LLM models before any usage. The model configuration is provided by the organization’s administrator. Both an LLM chat model and an embeddings models must be configured.

When configuring a model, the BYOM CLI requires several mandatory configuration fields. These values must be obtained from the selected model provider and supplied during the configuration process.

The following are the models supported by Agent v1.2.0.

Supported LLM providers

ProviderBaseline ModelRequired Parameters
openaigpt-5.2provider, api_key, model
azure-openaigpt-5.2-chatprovider, api_key, api_endpoint, api_version, model¹
anthropicclaude-sonnet-4-6provider, api_key, model
google-geminigemini-3.1-flash-liteprovider, sa_json², project_id, location, model

¹ For azure-openai, model is the Azure deployment name. ² For google-gemini, sa_json is the full contents of the Vertex AI service-account JSON key file.

Supported Embedding providers

Embedding models are a fixed allowlist — only the exact model shown below is accepted per provider.

ProviderSupported ModelRequired Parameters
openaitext-embedding-3-largeprovider, api_key, model
azure-openaitext-embedding-3-largeprovider, api_key, api_endpoint, api_version, model¹
google-geminigemini-embedding-001provider, sa_json², project_id, location, model
voyagevoyage-3provider, api_key, model

¹ For azure-openai, model is the Azure deployment name. ² For google-gemini, sa_json is the full contents of the Vertex AI service-account JSON key file.

Note: Anthropic does not offer an embedding API. Use voyage, openai, or azure-openai for embeddings when your LLM is Anthropic.

Last modified : October 29, 2026