Spinnaker "account ... not found" in CI

By Daniel Zoghalchali·Latchkey

A stage referenced a cloud provider account by name and Spinnaker has no such account configured, or the caller cannot see it. The deploy or bake cannot proceed without a valid account.

What this error means

A stage fails with "Account 'prod-k8s' not found" or "Unable to find account". The account name in the pipeline does not match a configured Clouddriver account.

Exception ( Deploy (Manifest) )
Account prod-k8s not found in clouddriver.
Known accounts: staging-k8s, dev-k8s

Common causes

The account name is misspelled or not configured

The pipeline references an account name that was never added to Clouddriver via Halyard, or the name differs.

The account exists but is not visible to the caller

Fiat authz or a not-yet-cached account can make a configured account appear "not found" to the execution.

How to fix it

Add or correct the provider account

1. List configured accounts and confirm the exact name.
2. Fix the pipeline reference, or add the account via Halyard and apply.
3. Re-run the pipeline once the account resolves.

hal config provider kubernetes account list
hal config provider kubernetes account add prod-k8s --context prod
hal deploy apply

Grant visibility in Fiat

If the account exists but is not visible, ensure the caller has permission and the account permissions include their role.

How to prevent it

• Keep account names consistent between pipelines and halconfig.
• Apply Halyard changes so new accounts are actually registered.
• Configure account permissions so authorized callers can see them.

Frequently asked questions

Related guides

References

• Terraform documentation
• GitHub Actions documentation