Use the Dashboard
Find any rollout, read what holds it and act on it.
On this page
Find an app or a rollout
Search reaches every app, rollout and pull request.
- Open Home for what needs you, or Rollouts, Apps and Environments for the whole fleet.
- Press Ctrl K (⌘ K on a Mac), or select Search at the top of the sidebar.
- Type part of a name.
- To find a pull request, paste its GitHub URL,
owner/repo#123or a commit sha, then select Open change #123 · repo.


Read a rollout
Progress shows where a release is, Gates what holds it.
- Open an app from Apps, then select the Progress tab.
- With several releases in flight, pick one in the release list. The drawing shows every environment, its regions grouped by Wave, and each place’s state: deployed, deploying, checking, held, waiting for approval, failed, or Not reached.
- Select a place in the drawing to open that rollout. When the app waits or failed, the banner above also has Open rollout; What the dashboard shows explains each banner.


- On the rollout, select the Gates tab. Gated by lists every gate, the environment before this one and the services it depends on, Downstream the rollouts that deploy after it. All dependencies › opens the dependency network.


- On a rendered-manifests rollout, select View source in the rollout header to read the deployed files (Rendered manifests).
Follow a change
The Changes page tracks each merged pull request through every service and environment.
- Open Changes. Your failing change, if any, leads in a banner.
- Select a change, then read its page.
| Where | What it shows |
|---|---|
| Attention | Your other failing changes, then approvals you can give |
| Your changes | Your repositories with a change in flight |
| Team | Other people’s repositories with a change in flight |
| Strip under the title | A row per service, a box per environment, a mark per region that opens its rollout |
| History and Summary | What happened, and the time from merge to the first deploy and to production |
Without a GitHub connection, these pages show Changes need GitHub.
Act on a rollout
Each action sits on a gate’s tile or the rollout page.
Approve a build
- On the Gates tab, find the approval gate that reads Needs you. It reads Needs approval when you cannot approve it.
- Select Approve. When the build waits in several regions, it reads Approve all and approves them all.
- Confirm the Approve build dialog with Approve.
Skip a gate once
- On the Gates tab, select Skip once on a schedule, approval or hand-written gate. Health checks and pins have no Skip once, and the button shows only when you may change the rollout.
- Read the dialog, Skip gate once: every other rule still applies, and the gate keeps holding every other build.
- Optionally select the other rollouts the gate holds, then confirm. When production is selected, type the build, or the gate’s name when the selected rollouts hold different builds.
Change version and pin
- On the rollout’s Overview, select Change version.
- Pick a build, or search by sha, version or commit.
- Turn on Pin build to keep the rollout on this build until you clear it. Without the pin, a build that is not the newest stays only until its bake succeeds, and then the rollout deploys the newest build its rules allow.
- In production, write why and type the build. Elsewhere the note is optional, and you type the build too when it failed on this rollout. Select Deploy to environment (Deploy anyway for a build that failed here, Roll back for an older build).


To follow new releases again, select Clear pin on the Overview banner or the pin’s tile.
Retry a failed deploy
- On the rollout’s Overview, select Retry on the Deployment failed banner.
- In production, or when a rule holds the build, confirm Redeploy to environment. When tests failed, it offers to retry or skip them.
Roll back
Start from one of two places:
- After a failed deploy: select Roll back on the Deployment failed banner of the rollout’s Overview. It deploys the build before the failed one.
- Any other build: select Roll back in the rollout header. It shows whenever an older build exists, and goes to the last older build this environment ran, else the release just below the running one. To pick the build yourself, choose an older one in Change version.
Then confirm. A rollback always pins, so the dialog has no Pin build switch. Select Roll back; in production, write why and type the build first.
The rollout stays on that build, under a Rolled back banner, until you select Clear pin. A force-deploy back does not hold: see Deploy a specific version.
Check the result
After Approve, the gate’s tile reads Approved. A skipped gate reads Skipped once for build until that build deploys.
Next steps
- Operate Operate with kubectl Pin a version, roll back, deploy a specific build, let a build past its gates, or resume after a failed bake.
- Gate deploys Require a Manual Approval Hold each new build of a Rollout until a person approves it in the dashboard or with kubectl.
- Gate deploys Set Deployment Windows Allow or deny deploys by time of day, day of week or date range.