Skip to main content

Intake Validation

Where your release is in its life

The bar on the release page shows five steps:

Draft → Ready for review → Under review → Ready to publish → Published

The release lifecycle bar with the six review stages expanded beneath it

StepWhat it meansWhat to do
DraftSaved, not submittedFinish it and submit
Ready for reviewSubmitted, waiting to startWait
Under reviewThe six checks are runningWatch the review stages
Ready to publishApprovedPublish it
PublishedLive on the App StoreNothing

A release can also come to rest off that line:

StateWhat it meansWhat to do
Pending approvalThe checks passed; a reviewer has not decided yetWait
Review failedA check failedFix it and submit the same release again
RejectedA reviewer declined itRead their reason under Errors and messages, address it, then submit again
ArchivedWithdrawn and no longer listedNothing

The six checks inside Under Review

Under review is where the work happens. It expands into six stages, ticked off as each passes.

CheckWhat it looks for
Metadata ValidationYour release details are complete and the version number is valid
Helm Chart ValidationYour chart is well-formed, it builds, and what it builds is a valid application
Secret ValidationThe secrets your chart asks for are actually in your vaults
Images ValidationYour credentials work and every image your chart needs can be downloaded
Test Application DeployYour application installs for real and starts up healthy
Armada ReviewA person at Armada approves it or turns it down
  Metadata ─▶ Helm Chart ─▶ Secret ─▶ Images ─▶ Test Deploy ─▶ Armada Review
│ │ │ │ │
└────────────┴───────────┴─────────┴───────────┘
any failure here stops the run
The run stops at the first failure

The checks run in order and stop as soon as one fails. The checks after it do not run at all.

So if Helm Chart Validation fails you will see nothing about your images — not because they are fine, but because they were never reached. Fix what failed and the next attempt gets further.


What each check does

Metadata Validation

Confirms your release details are filled in and that the Bundle version is a valid version number. The chart version is checked separately, in Helm Chart Validation.

Helm Chart Validation

The widest check — it has more ways to fail than any other.

Confirms your chart has Chart.yaml, values.yaml and a templates folder, builds it, and checks the result is valid Kubernetes. It also reads out the images your chart needs — a chart needing none is refused, since there would be nothing to install.

Try this yourself first

This check runs the same tools you can run on your own machine:

helm lint ./mychart
helm template ./mychart > built.yaml
kubectl apply --dry-run=client -f built.yaml
grep -E '^\s*image:' built.yaml # should list at least one image
grep '^version:' ./mychart/Chart.yaml # must equal the chart version you submit

A chart that gets through all five of those will usually pass this check.

Secret Validation

Checks that each vault your chart names exists and each secret inside it is there. If your chart names more than one vault, all have to resolve — one wrong name fails the check.

This step only looks; it creates nothing.

Images Validation

Confirms your credentials work and that every image your chart needs can be downloaded. All are checked, so one tag that has been deleted, renamed or mistyped fails the check.

Test Application Deploy

Installs your application on a real cluster and waits for it to start. The slowest check — it takes as long as your application takes to boot. A clearly dead deployment ends early rather than waiting it out: a container that keeps restarting, an image that will not download, one that runs out of memory, or one that will not fit.

Armada Review

Someone at Armada approves your release or turns it down. If turned down, their reason appears on the release page against this step — you do not have to ask.


Following along

Each check reports its own state, separate from the release step above:

Check stateMeaning
PendingAccepted, not started yet
RunningIn progress
SuccessEverything passed
FailedA check failed
CancelledYou stopped it

A failed check is listed by name under Errors and messages on the release page, with a message explaining what went wrong. Take that message to Troubleshooting intake.

Stopping a run

You can cancel a run while it is going; once finished you cannot. If a run is slow, cancel rather than resubmitting — a second submission of the same version is refused while the first is running.


Publishing

Publishing is your decision, not the reviewer's — an approved release sits at Ready to publish until you publish it.

Publish release asks where to publish, and asks you to accept the terms.

The Publish release dialog, with the Publish to dropdown and the agreement checkbox

Publish toWho can see it
Internal (Private Marketplace)Only your own Atlas Organization
External (Public Marketplace)Every Armada customer

You also have to tick I have read and agree, which covers the applicable Armada agreement and any terms it incorporates. Publish stays disabled until you do.

Remove listing takes the listing back down afterwards.