a6-recipe-blue-green

Implement blue-green deployments for APISIX using the a6 CLI.

1|2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/api7/a6 --skill a6-recipe-blue-green-api7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a6-recipe-blue-green
Source: https://github.com/api7/a6/tree/main/skills/a6-recipe-blue-green
Command: npx skills add https://github.com/api7/a6 --skill a6-recipe-blue-green-api7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blue-green deployments enable zero-downtime releases by maintaining two identical production environments and switching traffic between them seamlessly.

Core Features & Use Cases

  • Create two parallel upstream environments (blue and green) and their routes
  • Switch traffic instantly with route updates or using the traffic-split plugin
  • Rollback procedures to restore the previous live environment
  • Declarative workflows with a6 config diff and a6 config sync for auditable releases

Quick Start

Initialize blue-green deployment by creating blue and green upstreams, wiring a route to blue, and preparing a switch plan.

Frequently Asked Questions about a6-recipe-blue-green

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

FAQPage Schema
How do I implement blue-green deployment in APISIX for zero-downtime releases?

Blue-green deployment in APISIX is implemented by creating two parallel upstream environments and switching traffic between them via route updates or the traffic-split plugin. This enables zero-downtime releases with rollback procedures.

Can I use the a6 CLI to declaratively sync APISIX route configurations?

Yes, the a6 CLI supports declarative workflows using config diff and config sync commands. This allows you to apply auditable release configurations and manage route updates for blue-green upstream swaps.

What is the best way to split traffic between two upstreams during a release?

The best way to split traffic between two upstreams is using the APISIX traffic-split plugin. It allows you to route specific percentages of traffic to parallel environments, enabling controlled testing before a full upstream swap.

How do I rollback a blue-green deployment if the new release fails?

Rollback in a blue-green deployment is performed by restoring the previous live environment through route updates. This switches traffic back to the original upstream, ensuring immediate recovery from a failed release.

Do I need declarative config workflows to manage APISIX blue-green deployments?

Declarative config workflows are not strictly required but are recommended for managing APISIX blue-green deployments. Using a6 config diff and config sync provides auditable releases and safety guards when swapping upstreams.