canary-release

Implement canary deployments with metric-gated traffic shifting and automated rollback.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill canary-release-kalilurrahman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary-release
Source: https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts/tree/main/02-devops-infra/canary-release
Command: npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill canary-release-kalilurrahman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires httpx.

What problem does it solve? Deploying a new version to all users at once risks widespread outages when bugs slip through testing. This Skill implements a canary release strategy that gradually shifts traffic (1% → 5% → 25% → 100%) with automated metric gates, so issues affect only a small user slice before triggering rollback. ## Core Features & Use Cases - Argo Rollouts Configuration: Generates Kubernetes Rollout manifests with Istio traffic routing, staged weight steps, and Prometheus-based AnalysisTemplates for error rate, p99 latency, and success rate gates. - Nginx + Lua Alternative: Provides cookie-based sticky canary routing with an admin endpoint to adjust traffic weights when Istio is unavailable. - Automated Promotion Script: A Python CanaryManager that soaks each stage, queries Prometheus gates, and rolls back to 0% automatically on threshold breach. - Use Case: A team deploying a new payment service version routes 5% of traffic to the canary, verifies error rate stays under 1% for 10 minutes, then progressively promotes to 100% with automatic rollback if p99 latency exceeds 500ms. ## Quick Start Set up a canary release for my Kubernetes service using Argo Rollouts with Prometheus metric gates for error rate and latency.

Frequently Asked Questions about canary-release

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

FAQPage Schema
How do I set up a canary deployment on Kubernetes?

Use Argo Rollouts with a canary strategy defining staged setWeight steps (5%, 20%, 50%, 100%) and pause durations. Attach an AnalysisTemplate that queries Prometheus for error rate and latency, so promotion only proceeds when all metric gates pass.

How to do canary releases without Istio or a service mesh?

Use Nginx with Lua scripting to split traffic by weight between stable and canary upstreams. A shared dictionary stores the current weight, cookies provide sticky sessions, and an internal admin endpoint lets you adjust the percentage at runtime.

What metrics should gate canary promotion?

Gate on error rate (under 1%), p99 latency (under 500ms), and success rate (above 95%), queried from Prometheus against canary-labeled traffic. Compare against stable baseline rather than absolute values, and require multiple consecutive passing checks before promoting.

Can I canary a database schema migration?

No, schema changes are not reversible and should never be canaried. Deploy migrations separately with backward-compatible changes first, then canary the application version that uses the new schema.

Why is my canary analysis failing despite low error rates?

Analysis fails when canary traffic volume is too low for statistical significance or when metrics are not labeled to isolate canary requests. Ensure each stage receives enough requests and that Prometheus queries filter by the canary slot label.