#Use Canary Release

#Introduction

Canary Release enables controlled deployment of service updates through gradual traffic shifting and real-time monitoring. This functionality:

• Mitigates deployment risks in production environments
• Supports multiple release strategies (canary/blue-green/A/B testing)
• Provides automated rollback mechanisms
• Integrates with GitOps workflows

Core value: Safe and observable service version upgrades

#Features

• Manual/Automatic traffic control modes
• Header/path-based routing rules
• Real-time success rate/latency metrics
• CRD-based configuration for GitOps

#Enabling Canary Release

#Step 1: Access Service Configuration

1. Navigate: Service List > Target Service
2. Select Canary Release tab
3. Click Enable under Release Configuration

#Step 2: Configure Release Parameters

analysis:
  interval: 2m
  maxWeight: 50
  stepWeight: 10
  threshold: 10
maxResponseTime: 500
minSuccessRate: 95

#Routing Configuration Management

#Traffic Distribution

http:
- route:
  - destination: reviews-primary
    weight: 80
  - destination: reviews-canary
    weight: 20

#Header-Based Routing

- match:
  - headers: { "user-type": "internal" }
  route:
    - destination: reviews-canary

#Path-Specific Testing

- match:
  - uri: { prefix: "/api/v2" }
  route:
    - destination: reviews-canary
      weight: 20

#CanaryDelivery CRD Reference

#Metadata Requirements

#Specification Details

spec:
  delivertype: canary
  targetRef:
    name: reviews-v1
  trafficControl: system

#Monitoring & Validation

#Key Metrics

#Release States

1. Initializing ➔ 2. Progressing ➔ 3. Promoting ➔ 4. Completed

kubectl get canarydeliveries -n prod

#Operational Constraints

• Incompatible with existing service routing
• Requires unique service naming per cluster
• GitOps-managed services have limited UI controls
• Security policies remain active during release