System Operations on

Background Processing and Cadence

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

The application programming interface (API) process owns Policy’s background services. They are not separate Kubernetes Deployments. Each service performs a different task. One successful worker does not prove another worker completed its work. Native import and publication use Policy Integration Manager (PIM).

Services and Defaults

The following table summarizes each background service, its default cadence, and its purpose:

Service	Source Default	Purpose and Boundary
Discovery catalog refresh	Use `300` seconds.	Refresh Traverse inputs. Retain the prior snapshot after failed refresh.
Native policy import	Use `60` seconds.	Import external PIM policies into the Library when PIM is configured.
Automatic recompilation	Use `300` seconds.	Compile approved intent against fresh discovery and live inventory.
Publication	Use `5` seconds.	Process durable approved publication or withdrawal work asynchronously.
Protection reconciliation	Use `30` seconds.	Evaluate current revision and deployment evidence for protection progress.
Legacy activation	Use `30` seconds.	Check older deployed records. Do not substitute for governed revision evidence.

The configuration guide explains the distinction between chart values, process environment, and credentials. Record effective settings for the running release rather than relying on this table.

Automatic Recompilation of Approved Policies

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

Policy’s application programming interface (API) periodically recompiles approved policies against fresh discovery and live Policy Integration Manager (PIM) inventory. Source changes can alter generated output without changing an author’s intent. This background check does not replace human review or approval.

For example, fresh discovery can associate another location with an existing classification. The same approved intent can then produce different target artifacts. The worker validates the refreshed set before accepting compilation changes. It does not react immediately to each discovery change event.

Observe and Restart Policy

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

Use this task as the platform operator during routine checks or incidents. These diagnostic checks are not installation steps. Read the error before restarting. Restarting does not correct policy fields or missing Policy Integration Manager (PIM) object mappings. The application programming interface (API) process also owns background scheduling.

Prerequisites

Prepare the following:

Set CTX to the intended Kubernetes context.
Obtain workload-read access for logs, events, and configuration references.
Obtain policy:observability for metrics and policy:audit for restricted operation evidence.
Obtain separate deployment authority only when a restart requires it.
Obtain your platform hostname, trusted certificate authority (CA) bundle, and current access token.

Configure API Access

Complete the credential-safe request setup with your own user token in a dedicated Bash session. Then set the deployment endpoint and trusted CA file in that same shell: