Deployment status
The Deployments table shows how a deploy is configured. To see whether it's actually running, look at its pods, their phase, and their restarts.
Is my deploy running?#
Find its pods
Open Infrastructure→Pods. Every replica of a deploy is one pod. Pod names start with the deploy's ID, so a deploy with Replicas set to 3 should show three pods.
Check the phase
The Phase column should read Running for every pod. Pending means the pod hasn't started yet: it's waiting for a node, pulling the image, or starting the container. See Pod phases.
Watch for restarts
Open Deployments→⋮→View metrics and choose Restarts. A count that keeps climbing means the container starts and then exits. Three or more is flagged.
Read the logs
Deployments→⋮→Watch logs shows the container's own output, including the errors that come just before an exit.
The Pods page#
- Pod
- The pod's name, one per running replica.
- Phase
- The pod's lifecycle phase.
- Location
- The location the pod runs in.
- Cluster
- The DevLyft cluster within that location. It's internal and can change, so don't point DNS at it.
- Ports
- Host ports the pod exposes, as protocol and port.
Each pod's ⋮ menu offers Watch logs and View metrics scoped to that pod. The page refreshes from its Refresh control. If it shows Pod data is currently unavailable, pod status couldn't be loaded for your login. The deploy itself isn't affected.
Pod phases#
| Phase | Meaning |
|---|---|
| Pending | Accepted but not yet running: waiting to be scheduled onto a node, pulling the image, or starting. |
| Running | Scheduled onto a node, with at least one container running. |
| Succeeded | All containers exited successfully and won't restart. |
| Failed | All containers exited, and at least one failed. |
| Unknown | The pod's state couldn't be read from its node. |
Placement#
Before a deploy's pods can start, the deploy has to be placed on a cluster in its location. A deploy whose record shows placement.state: PENDING hasn't been assigned to a cluster yet, usually because the location doesn't have room for the environment yet. It retries on its own. Contact support if it stays pending.
Overview page#
Overview lists Recent Builds and Recent Deployments, a Deploys by tenancy breakdown (Shared, Dedicated, Inherit) and an organisation CPU usage chart. It's a quick way to confirm that new work landed.