kienbui1995/magic-powers/ado-container-deployments
Claude Code and agent skill by kienbui1995/magic-powers
Trust tier 3
- community
Source check pending
Checking that the SKILL.md file is still in the repository.
Use when implementing container CI/CD on Azure DevOps — Docker image builds with caching, pushing to Azure Container Registry, deploying to AKS with Helm or kubectl, and image promotion across environments.
Install
npx vskill@latest install kienbui1995/magic-powers/ado-container-deploymentsSKILL.md
The same SKILL.md was published earlier as kienbui1995/magic-powers/ado-container-deployments.
ADO Container Deployments
When to Use
- Building and pushing Docker images via Azure Pipelines
- Deploying containers to AKS or Azure Container Apps
- Implementing image promotion (dev image tag → staging tag → prod tag on same digest)
- Setting up Helm chart deployments via pipelines
- Managing multi-stage Docker builds in CI
- Adding vulnerability scanning to container pipelines
Core Jobs
1. Docker Build & Push to ACR
2. Deploy to AKS with kubectl and KubernetesManifest
3. Helm Deployments
4. Image Promotion Across Environments
5. Container Vulnerability Scanning
6. Azure Container Apps Deployment
Key Concepts
- ACR (Azure Container Registry) — Azure-native private registry; integrates with AKS natively via managed identity; no credentials needed when both in same subscription
- KubernetesManifest task — deploys K8s manifests with automatic image tag substitution; tracks deployments in ADO environments
- Image promotion — retag same image digest for different environments using
az acr import; ensures identical bits are tested and deployed - `--atomic` Helm flag — automatically rolls back a Helm release if deployment fails within the timeout; critical for production stability
- Environment namespace format —
environment: dev.myapp-namespacetracks deployments at Kubernetes namespace granularity in ADO environments tab - BuildKit inline cache — stores Docker layer cache in the registry itself using
--build-arg BUILDKIT_INLINE_CACHE=1; subsequent builds reuse layers without a separate cache registry
Checklist
- [ ] Docker builds use
--cache-fromfor registry-based layer caching? - [ ] ACR service connection uses managed identity or service principal (not ACR admin account)?
- [ ] Image promotion used across environments (retag, not rebuild) — same digest guaranteed?
- [ ] Helm deployments use
--atomicflag for automatic rollback on failure? - [ ] Container image scanned for HIGH/CRITICAL CVEs before deploying to production?
- [ ] AKS deployments use
KubernetesManifesttask for ADO environment tracking? - [ ]
checkout: nonein deploy jobs (source code not needed to deploy an image)?
Key Outputs
- Docker build pipeline with registry-based layer caching and ACR push in one stage
- Helm or kubectl deployment to AKS with ADO environment deployment tracking
- Image promotion pipeline (build once in CI, promote digest across dev/staging/prod)
- Trivy or Defender vulnerability scan as a quality gate before production deployment
Output Format
- 🔴 Critical — using ACR admin account in service connection (single set of credentials, hard to rotate), no vulnerability scan before production, rebuilding the image for each environment (different binary than what was tested)
- 🟡 Warning — no Docker layer caching configured (full rebuild on every run, slow), Helm deployed without
--atomic(partially failed releases left in broken state with no auto-rollback) - 🟢 Suggestion — use
--cache-fromfor 50-80% faster Docker builds on unchanged layers, add Trivy scan as quality gate to catch CVEs before they reach production, useaz acr importfor image promotion to guarantee immutable image across environments
Anti-Patterns
- Using ACR admin username and password in service connection — a single non-rotatable credential with full registry access
- Rebuilding the Docker image for staging and production instead of promoting the dev image — the binary in production has never been tested
- Helm deploy without
--atomic— a failed upgrade leaves the release in a partially updated state with no automatic recovery - Pulling
:latesttag from registry in deployment manifests — non-deterministic, a new image push during deployment can cause split-brain clusters - Running vulnerability scans only locally before push, not in the pipeline — bypassed by any developer
Integration
ado-pipeline-design— structure the container build and deploy pipeline with proper stage dependenciesado-release-management— add approval gates and Azure Monitor checks to container deployment stagesado-pipeline-security— harden ACR service connection permissions and scan images for vulnerabilitiesado-pipelines-ops— create service connections for ACR and AKS with appropriate RBAC roles
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/ado-container-deployments/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/kienbui1995/magic-powers/ado-container-deployments)