Data Discovery on

Prerequisites

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

Ensure that the following prerequisites are met before installing Data Discovery with PPC:

PPC Cluster Team Edition must be installed and accessible. For more information on installing PPC, refer Installing PPC for instructions.
Access to a Kubernetes cluster with sufficient permissions to manage the following resources:
- Namespace
- Deployment
- Service
- ConfigMap
- Secret
- HorizontalPodAutoscaler
- Gateway API resources (HTTPRoute, ReferenceGrant, SecurityPolicy)
- Karpenter resources (NodePool, EC2NodeClass)
Authorization to provision AWS m5.large instances.
Ensure that the jumpbox can connect to the required repositories. If not already authenticated, then log in to the required repository.

Installing Data Discovery

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

Data Discovery application can be deployed using helm.

Note: For connecting and deploying from the Protegrity Container Registry (PCR), use the helm registry login <Container_Registry_Path> command and the credentials obtained from the My.Protegrity portal during account creation.

Install Data Discovery using the following command:

helm registry login <Container_Registry_Path>
helm upgrade --install data-discovery \
 oci://<Container_Registry_Path>/data-discovery/2.0/classification/helm/data-discovery \
 --version 2.0.0-373.gf464fa3e \
 --namespace data-discovery \
 --create-namespace

Replace the placeholder values in the command with the following variables.

Configuring Data Discovery

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

This section provides guidance on configuring Data Discovery logging and service providers.

Configurations can be set during deployment by overwriting the configurations defined in the Data Discovery Helm values.yaml.

Overriding Configurations

Create a values-override.yaml file with the custom configuration mentioned in the Logging Configuration.
Save the changes.
If the application is already deployed, uninstall it using the following command.
```
helm uninstall data-discovery -n data-discovery
```
Run the installation command mentioned in the Installing Data Discovery.

Uninstalling Data Discovery

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

Run the following command to uninstall:

helm uninstall data-discovery -n data-discovery

Tip: If the uninstall process hangs, refer to the Manually remove the remaining resources in the Troubleshooting section.

Troubleshooting

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

The following section provides a quick reference for common issues, their causes, and actions.

Pods remain in the Pending state.
- Likely cause: The NodePool is not ready or does not have sufficient capacity.
- Action: Check the NodePool status and verify that sufficient capacity is available.
HPA displays unknown metrics.
- Likely cause: The Metrics Server is missing or unhealthy.
- Action: Install the Metrics Server or restore its health.
Gateway API returns a 401 Unauthorized response.

Logging usage metrics

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

Data Discovery generates usage logs for all classification requests submitted to the service. These logs provide visibility into how the service is being used and support monitoring, auditing, and operational analysis. Usage logs include high-level metrics such as request outcomes and the volume of data processed, enabling administrators to track usage patterns and assess service behavior over time.

For a detailed description of the usage log format and available fields, see the
Data Discovery Usage Logs documentation.