Skill

orchestrating-deployment-pipelines

Orchestrates multi-stage deployment pipelines with Kubernetes, CI/CD platforms, and strategies like blue-green, canary, rolling updates across dev/staging/prod.

Docker

Kubernetes

From deployment-pipeline-orchestrator

Install

Run in your terminal

npx claudepluginhub nickloveinvesting/nick-love-plugins --plugin deployment-pipeline-orchestrator

Tool Access

This skill is limited to using the following tools:

ReadWriteEditGrepGlobBash(git:*)Bash(docker:*)Bash(kubectl:*)

Supporting Assets

View in Repository

assets/README.md

assets/example_config.yaml

assets/pipeline_template.yaml

references/README.md

scripts/README.md

scripts/init_pipeline.sh

Skill Content

Similar Skills

ui-ux-pro-max

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

57.6k

context7-mcp

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

51.4k

market-sizing-analysis

2 files

Calculates TAM/SAM/SOM using top-down, bottom-up, and value theory methodologies for market sizing, revenue estimation, and startup validation.

startup-business-analyst

32.9k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 20, 2026

Actions

View Source View Plugin View on GitHub View README

Orchestrating Deployment Pipelines

Overview

Orchestrate multi-stage deployment pipelines that coordinate builds, tests, approvals, and releases across environments (dev, staging, production). Implement deployment strategies including blue-green, canary, rolling updates, and feature flags using Kubernetes, cloud-native services, and CI/CD platforms.

Prerequisites

CI/CD platform configured (GitHub Actions, GitLab CI, Jenkins, ArgoCD)
Kubernetes cluster with kubectl access or cloud deployment target (ECS, Cloud Run, App Engine)
Container registry with built and tagged images ready for deployment
Environment-specific configuration (secrets, environment variables) stored securely
Monitoring and alerting configured to detect deployment failures

Instructions

Define the deployment topology: target environments, promotion flow (dev -> staging -> production), and approval gates
Select deployment strategy per environment: rolling update for staging, canary or blue-green for production
Generate deployment manifests (Kubernetes Deployments, Services, Ingress) or cloud service configurations
Implement pre-deployment checks: database migration status, dependency health, configuration validation
Configure canary analysis: route 5-10% of traffic to new version, monitor error rate and latency for 15 minutes before full rollout
Add post-deployment verification: smoke tests, health check endpoints, synthetic monitoring
Implement automated rollback triggers: revert if error rate exceeds 1% or P99 latency doubles during canary phase
Set up deployment notifications: Slack messages with deployment status, version, environment, and commit link
Document the deployment runbook with manual intervention procedures for edge cases

Output

Deployment pipeline configurations (GitHub Actions workflows, ArgoCD Applications)
Kubernetes manifests with deployment strategy annotations
Canary analysis configuration (Flagger, Argo Rollouts)
Pre/post-deployment hook scripts
Deployment runbook with rollback procedures

Error Handling

Error	Cause	Solution
`ImagePullBackOff`	Image tag not found in registry or auth failure	Verify image exists with `docker manifest inspect`; check `imagePullSecrets`
`CrashLoopBackOff`	Application failing to start in new version	Check pod logs with `kubectl logs`; verify environment variables and config maps
`Canary analysis failed`	Error rate or latency exceeded threshold during canary	Automatic rollback triggered; investigate logs from canary pods before retrying
`Deployment stuck in Progressing`	Insufficient resources or pod scheduling failure	Check `kubectl describe deployment` for events; verify resource requests and node capacity
`Database migration failed`	Schema conflict or lock timeout	Run migrations independently before deployment; add retry logic and connection timeout

Examples

"Create a deployment pipeline that builds on PR merge, deploys to staging automatically, runs integration tests, then requires manual approval for production with canary rollout."
"Set up Argo Rollouts for a Kubernetes deployment with 10% canary traffic, Prometheus-based analysis, and automatic rollback on error rate > 0.5%."
"Generate a blue-green deployment for an ECS service with ALB target group switching and automatic rollback on health check failure."

Resources

Kubernetes deployment strategies: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/
Argo Rollouts: https://argoproj.github.io/argo-rollouts/
Flagger (progressive delivery): https://flagger.app/
AWS ECS blue-green: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-bluegreen.html