Skip to content

Getting Started with Runtime Plane

Most setup is in the portal (Settings → Runtime Plane): create the runtime plane, configure connectors, and follow the on-screen steps. This page summarizes how the runtime behaves and what you might do outside the form — without repeating field-level help the UI already provides.

How configuration and status move

Direction What happens
You → portal You enter runtime plane and connector settings.
Agent → Runtime Manager The agent polls for configuration and pushes status (agent health and connector state) to Runtime Manager.
Agent ↔ connectors The agent manages connector workloads. Connectors poll the agent for updates to the configuration properties they consume.

One-time secrets

When the runtime plane is created, the portal shows secrets only once (for example the Runtime Agent API key and the private encryption key for connector fields). Copy them safely before closing the dialog; they are not shown in full again except a new API key after Regenerate. How Sensitive Data is Handled explains Privacera Managed keys, where connector secrets can live (Privacera Cloud vs Kubernetes vs cloud native), and how they are protected; those credentials and connector secrets are consumed during provisioning and runtime according to your deployment.

Provisioning the Runtime Agent

  • D2P — Follow the portal-guided steps for your Privacera-managed account and self-managed cluster in your cloud.

After the runtime plane is live

  • Change connectors and settings in the portal; the agent reconciles them and connectors pick up property updates by polling the agent.
  • For runtime plane and connector configuration changes and health, use the Privacera portal.
  • To troubleshoot pods and check logs, use the Kubernetes cluster.