Domäne
DevOps & CI/CD
Skill-Profil
Weighted routing, metrics-based promotion, automated rollback, A/B testing
Rollen
5
wo dieser Skill vorkommt
Stufen
5
strukturierter Entwicklungspfad
Pflichtanforderungen
21
die anderen 4 optional
DevOps & CI/CD
Deployment Strategies
17.3.2026
Wählen Sie Ihr aktuelles Level und vergleichen Sie die Erwartungen.
Die Tabelle zeigt, wie die Tiefe von Junior bis Principal wächst.
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Cloud Engineer | Pflicht | Understands the fundamentals of Canary Deployment. Applies basic practices in daily work. Follows recommendations from the team and documentation. |
| DevOps Engineer | Understands canary deployment concept: gradual rollout of new version to a portion of traffic. Knows differences from blue-green, understands the role of metrics in promotion decisions. Observes the canary deployment process. | |
| DevSecOps Engineer | Studies canary deployment concept: gradual rollout to a percentage of traffic with monitoring. Configures simple canary through Kubernetes with two Deployments and weighted routing. Monitors metrics (error rate, latency) during canary phase. Understands promote or rollback criteria. | |
| Platform Engineer | Pflicht | Understands the canary deployment concept and how it differs from blue-green for the platform. Monitors canary release metrics via Grafana/Prometheus. Escalates issues when metrics degrade. Participates in configuring traffic split through ArgoCD Rollouts by following instructions. |
| Release Engineer | Pflicht | Understands the canary deployment concept: gradually increasing traffic to the new version. Knows how to monitor canary and make rollout or rollback decisions. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Cloud Engineer | Pflicht | Independently creates and maintains Canary Deployment. Configures CI/CD pipelines. Automates routine operations. |
| DevOps Engineer | Implements canary deployments through Argo Rollouts or Istio: configuring promotion steps (10%→30%→70%→100%), integration tests between steps. Defines analysis metrics (error rate, latency, saturation), configures automated rollback. | |
| DevSecOps Engineer | Implements canary deployment with ArgoCD Rollouts and Istio/Nginx for traffic splitting. Configures analysis templates: Prometheus queries for automated canary evaluation (error rate < 1%, p99 < 500ms). Introduces progressive delivery: 5% → 25% → 50% → 100% with automated analysis at each step. | |
| Platform Engineer | Pflicht | Configures canary deployment through Argo Rollouts: AnalysisTemplate, traffic management via Istio/NGINX. Defines canary metrics (error rate, latency p99, saturation). Automates promotion/rollback based on analysis runs. Creates canary templates for platform teams. |
| Release Engineer | Pflicht | Configures canary deployment with traffic splitting (Istio, Argo Rollouts). Defines success criteria and automated rollback triggers. Implements A/B testing within canary deployments. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Cloud Engineer | Pflicht | Designs CI/CD architecture with Canary Deployment. Optimizes pipeline speed and reliability. Introduces progressive delivery. |
| DevOps Engineer | Pflicht | Designs canary deployment platform: Argo Rollouts with analysis templates, Prometheus metrics for automatic promotion/rollback. Implements Flagger for service mesh-based canary, configures custom metrics and webhook analyzers. |
| DevSecOps Engineer | Pflicht | Designs advanced canary strategy with multi-metric analysis and machine learning anomaly detection. Introduces Flagger for automated canary deployments with custom webhooks. Configures canary for stateful services with database compatibility checks. Develops observability stack for detailed canary comparison. |
| Platform Engineer | Pflicht | Designs canary infrastructure for IDP: multi-metric analysis, header-based routing for internal canary. Integrates canary with observability stack (Prometheus metrics + custom analysis). Creates self-service canary configuration with safe defaults for all teams. |
| Release Engineer | Pflicht | Designs canary strategy with statistical significance testing. Implements progressive traffic shifting with automated analysis (Flagger). Ensures observability for canary comparison. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Cloud Engineer | Pflicht | Defines DevOps strategy with Canary Deployment. Establishes CI/CD standards. Introduces platform engineering approaches. |
| DevOps Engineer | Pflicht | Defines progressive delivery strategy for the organization: canary analysis standards, mandatory metrics and SLO thresholds for promotion. Designs unified delivery pipeline with automated canary for all service types, incident management integration. |
| DevSecOps Engineer | Pflicht | Defines Progressive Delivery strategy with canary as primary deployment pattern. Manages canary deployment platform for all teams. Builds effectiveness metrics: canary duration, auto-rollback rate, detection accuracy. Introduces canary for infrastructure changes, not just application deployments. |
| Platform Engineer | Pflicht | Defines organizational progressive delivery strategy: canary + feature flags + observability as a unified process. Leads automated canary analysis adoption across all services. Designs blast radius management through graduated rollout policies and automatic halts. |
| Release Engineer | Pflicht | Defines canary deployment standards and success metrics for the platform. Makes decisions on automation vs manual approval gates. Manages rollout risk. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Cloud Engineer | Pflicht | Defines platform-level canary deployment strategy: progressive delivery through Flagger/Argo Rollouts, weighted traffic shifting through service mesh, automated rollback based on SLO metrics. Designs observability pipeline for canary analysis and integration with cloud-native load balancers. |
| DevOps Engineer | Pflicht | Develops automated progressive delivery architecture: ML-driven canary analysis, automatic deployment strategy selection, chaos engineering integration. Defines safe deployment standards for organizations with thousands of deployments per day. |
| DevSecOps Engineer | Pflicht | Architecturally defines Progressive Delivery approach for multi-service platform. Designs unified deployment pipeline: build → canary → promote → full rollout with automated quality gates. Defines SLO-based deployment decision standards. Develops continuous verification framework for production. |
| Platform Engineer | Pflicht | Shapes vision for intelligent release management: ML-powered canary analysis, automated experiment design. Defines confidence-based deployment strategy for the organization. Evaluates advanced techniques: shadow traffic, synthetic canary, chaos-informed releases for reliable platform. |
| Release Engineer | Pflicht | Shapes progressive delivery strategy for the organization. Researches automated deployment analysis with ML. Influences deployment risk management approaches. |