GitOps Progressive Delivery Canary Deployment Specification

Role: Lead Platform SRE Architect with deep expertise in GitOps synchronization engines, service meshes, and automated remediation.

Context

• Target Kubernetes cluster tier and topology: {{kubernetes_cluster_tier}}
• GitOps controller and synchronization engine: {{gitops_tooling}}
• Service mesh or ingress traffic router: {{traffic_manager}}
• Primary golden signal metrics and SLO thresholds: {{slo_metrics}}
• Automated rollback thresholds and criteria: {{rollback_triggers}}
• Canary traffic ramp-up schedule and evaluation intervals: {{canary_step_intervals}}

Task

Produce an exhaustive engineering specification for a GitOps-driven progressive delivery canary system that manages traffic shifting, real-time telemetry validation, and automated rollback orchestration.

Method

1. Define the repository structure, branch synchronization, and CRD manifests for {{gitops_tooling}}.
2. Configure traffic splitting mechanisms via {{traffic_manager}} to decouple release from deployment.
3. Translate {{canary_step_intervals}} into step-by-step traffic weight percentage tiers and stabilization pauses.
4. Specify statistical metric analysis queries against {{slo_metrics}} for each evaluation interval.
5. Design automated fast-rollback mechanisms that execute immediately upon violating {{rollback_triggers}}.
6. Establish GitOps reconciliation locks during active canary cycles to prevent state drift.
7. Detail post-promotion cleanup, baseline synchronization, and incident webhook notification payloads.

Constraints

• MUST define automatic, zero-human-intervention rollbacks if {{rollback_triggers}} are breached.
• MUST NOT allow GitOps drift reconciliation to override an ongoing canary state machine.
• Traffic shifts must strictly adhere to the intervals specified in {{canary_step_intervals}}.
• Health evaluation metrics must be derived exclusively from {{slo_metrics}} baseline parameters.

Output format

Deliver the document using the following structured sections:

1. Progressive Delivery System Architecture
2. Traffic Routing & Canary Split Configuration
3. Metric Analysis & Decision Engine Matrix
4. Rollout Schedule & Step Progression Table
5. Fast-Rollback State Machine & Alert Routing Total word count: 900–1,300 words.

Self-review

• Validate that metric queries in section 3 map directly to {{slo_metrics}}.
• Ensure rollback mechanisms are guaranteed to be fully automated without human confirmation.
• Check that GitOps synchronization conflicts with active canary steps are explicitly mitigated.