Protegrity Agent on

Prerequisites

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

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

Infrastructure

The jumpbox is registered and prepared.
For more information, refer to Configuring Authentication for Protegrity AI Team Edition.
Access to the OCI registry is available.

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:

Installing Protegrity Agent

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

The Protegrity Agent v1.2.0 can be installed using helm chart 2.0.0. The helm chart deploys the following components.

Component	Description
Protegrity Agent Service	Main application service
PostgreSQL Database	Persistent database
Web UI	Web interface for Protegrity Agent

Installing Protegrity Agent

Perform the following steps to install Protegrity Agent.

1. Creating Namespaces and Database Secrets

The namespaces and Database secrets must be created only once per cluster. These can be reused for subsequent upgrades and re-installs. Ensure to only replace the Secret when rotating credentials.

Creating Agent Users

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

Agent users must have one or more roles that determine their permissions and capabilities.

The Protegrity Agent Helm chart creates the required roles during installation. Assign them to separate PPC user accounts or combine them with other roles on a single account. To assign multiple roles, provide a comma-separated list.

When assigning Agent roles to an account that already has roles for other PPC products or features, include every role the account should retain. Updating a user’s roles replaces the existing role list. For instructions on creating users and managing role assignments, see the PPC Admin CLI user-management instructions.

Configuring BYOM

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

Supported Models

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.

For more information about the supported models and configurations, refer to Supported Models.

Configuring BYOM

Before you begin

If a PPC CLI session was opened before installing the Agent, it will not detect the new installation. After installing the Agent, start a new PPC CLI session before configuring BYOM. Do not reuse an existing session. This applies whenever you configure or update BYOM, not only immediately after installation. If the base Agent URL has changed, exit all existing sessions gracefully and start a new session so it uses the updated URL.

Accessing the Agent

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

To access the Protegrity Agent in the Web UI, use a PPC user account assigned the agent-user role. For example, you can create an account named proagent-user. For instructions, refer to Creating Agent Users.

Access the Agent using the FQDN provided during the installation process.

https://<cluster-FQDN>

Enter the following parameters to log in and view the homepage.

Username: Username of the user with agent-user role.
Password: Password of the user with agent-user role.

For more information about the credentials and role management, refer to Log in to PPC.

Uninstalling the Agent

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

The following procedure removes Protegrity Agent 1.2.0 (Helm chart 2.0.0) from supported AWS and Azure PPC environments. If custom resource names were used during installation, substitute the default names in the commands accordingly.

Before beginning the uninstallation process, verify that the correct Kubernetes context is selected and back up any required data, credentials, or configuration information stored outside the Agent volumes. The uninstallation process may remove resources such as the backup Persistent Volume Claim (PVC) and the database Secret created through External Secrets.