Configure Policy

Platform operators configure Policy through the selected chart and approved secret management. Protegrity Provisioned Cluster (PPC) administrators control human and dependency access. Use nonsecret customer values to record deployment choices reproducibly. A chart value controls generated Kubernetes resources. An environment variable configures the running backend process. A credential Secret supplies sensitive values. Changing one does not automatically change the underlying account.

Choose a Reference

Choose the reference that matches the setting:

• Refer to Security settings to distinguish human capabilities, resource grants, worker credentials, network access, and signing keys.
• Refer to installation prerequisites for required platform and identity inputs.

Apply a Configuration Change

Apply a reviewed change through the release configuration:

1. Identify the owner and impact of the setting. Record whether it changes credentials, storage, schema, scheduling, or target access.
2. Compare your current release values with the selected chart defaults. Do not assume a new default overrides an existing explicit value.
3. Update your reviewed nonsecret override file. Keep passwords, tokens, and private keys in approved secret management.
4. Ask the platform and database administrators to confirm the procedure, downtime, and recovery plan before applying another chart revision.
5. Repeat installation verification. Refer to installation verification. Confirm effective settings through system operation. Refer to System operations.

Do not edit generated ConfigMaps as a lasting configuration method. Helm can overwrite those edits, and existing processes may retain old values. A healthy rollout does not establish correct downstream identity or protection.

For ongoing work, refer to background processing and automatic recompilation.