Overview
A deployment in Platz is a single Helm release that Platz manages on your behalf. Each deployment maps one-to-one with a Kubernetes namespace, a Helm release inside that namespace, and a row in the deployments table.
How Deployments are Tracked
Platz keeps an opinionated, live picture of what your deployments are doing in their target clusters. This page explains how the tracking works — what gets recorded, how, and where the limits are — so you know what to trust and what not to.
Importing Existing Deployments
If you've been running Helm releases by hand or through CI scripts, and want Platz to take them over, there's a manual import path. Platz doesn't have a one-click "import" button — but the steps are simple enough.
Tasks & History
Everything Platz does to a deployment is recorded as a task — a row in the deploymenttasks table that describes what should happen, who triggered it, and what_ the outcome was. The History tab on each deployment is a paginated view of that table, newest first.
Deployment Credentials
When Platz installs a chart, it needs to give the chart's pods a way to authenticate back to Platz — both for the Status feature (where the chart's pod serves a status endpoint that Platz polls) and for the Invoke Action feature (where Platz's pods call back into the chart's HTTP endpoints).
Status
The Status feature lets a chart's pods report a structured health document back to Platz, which renders it in the deployment's UI — a color-coded badge, optional warning notices, optional numeric metrics, and an optional "primary metric" shown directly in the deployment list.