Configuring Protegrity Agent
Steps to configure Protegrity Agent
API Service Endpoints
This section provides an overview of the service API endpoints exposed by Protegrity Agent.
| Name | Endpoint |
|---|---|
| Conversations | /pty/proagent/v1.0/conversations |
| Responses | /pty/proagent/v1.0/responses |
| Health Check | /pty/proagent/v1.0/health |
| Readiness Probe | /pty/proagent/v1.0/ready |
| Liveness Probe | /pty/proagent/v1.0/live |
| Version Info | /pty/proagent/v1.0/version |
| UI Dashboard | /pty/proagent/v1.0/ui |
Protegrity Agent Configurations
In addition to the OpenAI endpoints, the following parameters are configurable through a user-provided my-values.yaml file, supplied during deployment using the helm upgrade ... -f my-values.yaml command.
| Section | Variable | Comment |
|---|---|---|
| global | restore | Restore mode flag. When true, Velero restores the backup PVC from S3 and a restore Job imports the pg_dump into a fresh Postgres instance. |
proagentService.environment | LOG_LEVEL | Application log level (default: INFO) |
proagentService.environment | THINKING_TIMEOUT | Agent pauses and asks for feedback if it goes over this limit (in minutes). Must be less than the application’s internal response timeout or any other network timeouts. |
backup | enabled | Backup status |
backup | schedule | pg_dump CronJob schedule |
backup | veleroSchedule | Velero snapshot schedule (30-min offset) |
backup | scheduleName | Backup name |
backup | backupName | Set to a specific backup name for point-in-time restore |
Updating the Deployment
To update the deployed cluster it is recommended to create a my-values.yaml and then helm upgrade ... -f my-values.yaml.
helm upgrade --install protegrity-agent \
oci://<container_registry_path>:9443/protegrity-agent/1.0/helm/protegrity-agent \
--set karpenterResources.nodeClass.amiId="<ami-id>" \
--version 1.0.0 \
--namespace pty-protegrity-agent \
--create-namespace \
-f my-values.yaml
Ensure that
The following table provides the list of AMI IDs
| Region | AMI ID |
|---|---|
| ap-south-1 | ami-07959c05dcdb79a72 |
| eu-north-1 | ami-0268b0bfff0f25d31 |
| eu-west-3 | ami-0ea9454aef60045a2 |
| eu-west-2 | ami-0d5eee57a6a1398a3 |
| eu-west-1 | ami-00a8d14029b60a028 |
| ap-northeast-3 | ami-0e495c3ffd416c65e |
| ap-northeast-2 | ami-0fc18a24aec719c1c |
| ap-northeast-1 | ami-00ec85b83bf713aac |
| ca-central-1 | ami-03891f0d8b41eb296 |
| sa-east-1 | ami-0a30f044a5781b4e0 |
| ap-southeast-1 | ami-0ae51324bf2e89725 |
| ap-southeast-2 | ami-0ef7e8095b163dc42 |
| eu-central-1 | ami-00e36131a0343c374 |
| us-east-1 | ami-07e4e828a19159636 |
| us-east-2 | ami-0e486911b2d0a5f7e |
| us-west-1 | ami-01183e1261529749e |
| us-west-2 | ami-04f850c412625dfe6 |
After upgrading the parameters successfully, execute the following command.
kubectl rollout restart protegrity-agent -n pty-protegrity-agent
Feedback
Was this page helpful?