canary

Automate canary deployments on Cloud Run with health checks and rollback.

159|41|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/atelier-fashion/adlc-toolkit --skill canary-atelier-fashion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/atelier-fashion/adlc-toolkit/tree/main/canary
Command: npx skills add https://github.com/atelier-fashion/adlc-toolkit --skill canary-atelier-fashion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canary deployments reduce production risk by validating new changes on a zero-traffic revision before full rollout.

Core Features & Use Cases

  • Zero-traffic canary deployments to test new revisions without affecting users
  • Automated health checks and smoke tests to verify runtime readiness
  • Safe promotion to production or rollback on failure

Quick Start

To begin a canary deployment, ensure gcloud is authenticated and a pre-existing Cloud Run service exists, then invoke the canary workflow with the target service name.

Frequently Asked Questions about canary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run canary deployments on Cloud Run without affecting production traffic?

Canary deployments on Cloud Run use zero-traffic revisions to test new changes safely. This Skill automates deploying a canary revision, tagging it, and capturing a canary URL to run health checks before routing any user traffic.

What are the prerequisites for automating a canary deployment with smoke tests?

Automating canary deployments requires gcloud authentication, access to a Docker image, and a pre-existing configured Cloud Run production service. You must also be able to capture a canary URL for post-deploy smoke tests and health checks.

How does automated rollback work when a canary health check fails?

Automated rollback triggers when post-deploy smoke tests or health checks fail. The canary deployment workflow verifies runtime readiness on the zero-traffic revision and safely rolls back the Cloud Run service if checks fail.

Can I use this canary deployment workflow for a new Cloud Run service?

No, this canary workflow works exclusively for pre-existing Cloud Run services. It requires a configured production service to deploy zero-traffic revisions and run automated health checks without affecting existing users.

What is the difference between a zero-traffic revision and a full production rollout?

A zero-traffic canary revision deploys new code without routing user traffic, allowing automated smoke tests to verify runtime readiness. A full production rollout promotes the canary revision to receive traffic after health checks pass.

When should I use canary deployments instead of rolling updates?

Canary deployments are best when validating new changes with automated health checks before full rollout. They reduce production risk by testing a zero-traffic revision and enabling safe rollback if smoke tests fail.