Read the project summary#

Open Projects and select a project. Compare the configured revision, desired state, observed resource health and last retained release. These are separate facts: the last successful release can be healthy while a newer desired revision is out of sync.

  1. Check the source, renderer, environment and target.
  2. Open the resource inventory and inspect changed, missing or unhealthy objects.
  3. Check the observation time before relying on a drift/health badge. A stale observation needs a fresh check.
  4. Follow the active or recent run to see whether the desired change is planned, blocked, awaiting approval or already applied.
The summary distinguishes the retained release, current desired/live observation and active run. A healthy retained release can coexist with a newer change awaiting approval.
The summary distinguishes the retained release, current desired/live observation and active run. A healthy retained release can coexist with a newer change awaiting approval. View full size ↗

Inspect resource changes#

Use the resource panel to inspect object identity, ownership and available detail/diff information. A resource count alone does not show the significance of a change. Review namespace, kind and action, especially when a plan includes deletion or changes to cluster-wide objects.

Plan/artifact access can require a permission separate from basic project viewing. An inaccessible diff is not an empty diff.

The Resources tab lists retained objects with their health, drift and planned action. Use these signals to decide which object needs closer inspection.
The Resources tab lists retained objects with their health, drift and planned action. Use these signals to decide which object needs closer inspection. View full size ↗

Edit a project#

  1. Open Edit and change only the source/revision, renderer, destination, policy or automation settings needed.
  2. Review prune, polling and verification settings before saving. Pruning authorizes removal of inventory-managed objects absent from desired state.
  3. Save and resolve any version conflict by refreshing and reviewing the latest configuration.
  4. Preview the new configuration. Previous approval or release evidence does not automatically cover a changed plan.
Edit project configuration changes future delivery inputs. It does not rewrite the evidence retained for previous runs.
Edit project configuration changes future delivery inputs. It does not rewrite the evidence retained for previous runs. View full size ↗

Automation modes#

ModeHow to approach it
manualUse explicit actions to create the delivery attempts you want. Appropriate for a first rehearsal.
previewUse source automation to evaluate proposed changes without assuming they have been applied.
autoAllow configured source automation to progress through its delivery gates. Policy, approval, windows and target restrictions still apply.

Polling interval, jitter and path patterns determine when and which source changes are evaluated. Auto does not mean unconditional execution.