Manage deployments

Use deployment groups, approvals, and status handling to coordinate and control how deployments are run across scopes.

Deployment groups

A deployment group lets you deploy to multiple scopes at once. While each deployment runs independently, the group provides centralized visibility and control.

Key behaviors

• Flexible grouping: Include scopes of any type or environment.
• Individual control: Cancel or roll back specific deployments at any time.
• Group status: The group is marked FINALIZED only when all deployments reach a terminal state.
• Cancellation rules: Groups can be canceled while they are still in progress, that is, while they are waiting for an approval or while their deployments are being created, waiting for instances, or running. Once the group starts finalizing, it can no longer be canceled.
• Rollback behavior: Rollback is allowed unless the group is FINALIZING.

Approvals and policies

Approval policies help enforce control over critical deployments by requiring explicit review before they proceed.

Examples

• Block production deployments during a holiday freeze
• Require approval from a senior engineer for sensitive scopes
• Auto-deny deployments by non-whitelisted users in production

When a deployment is denied during approval, its status becomes CREATING_APPROVAL_DENIED.

See the Approvals guide to learn how to create and manage policies.

Deleted deployments

There's a special situation where an active deployment is not replaced by a new one. This occurs when a scope is stopped, and the deployment status is set to DELETED.

Note: This only applies to Kubernetes and server instance scopes.

Next steps

For details on how deployments progress through lifecycle stages, see Deployment lifecycle and flow.