How do you actually separate CI/CD pipelines for AKS across dev/qa/uat/prod in Azure DevOps?
📰 Reddit r/devops
Separate CI/CD pipelines for AKS across dev/qa/uat/prod in Azure DevOps using environment-specific YAML files and variables
Action Steps
- Create separate YAML files for each environment (dev, qa, uat, prod) using Azure Pipelines
- Define environment-specific variables in the YAML files to control deployment settings
- Use the KubernetesManifest@1 task to deploy to each environment
- Configure environment-specific deployment strategies (e.g., canary, blue-green) using Azure Pipelines
- Test and validate deployments in each environment before promoting to production
Who Needs to Know This
DevOps teams and engineers working with Azure DevOps and AKS can benefit from this approach to manage complex CI/CD pipelines across multiple environments
Key Insight
💡 Separating CI/CD pipelines by environment allows for more control and flexibility in managing deployments to different stages
Share This
🚀 Separate CI/CD pipelines for AKS in Azure DevOps using env-specific YAML files and variables #AzureDevOps #AKS #CICD
Key Takeaways
Separate CI/CD pipelines for AKS across dev/qa/uat/prod in Azure DevOps using environment-specific YAML files and variables
Full Article
Hey Folks, need your advice badly , I'm building out a CI/CD flow for AKS using Azure DevOps Pipelines (not ArgoCD/GitOps for this one, using native Azure Pipelines + KubernetesManifest@1 tasks). Trying to understand what people actually do in production. The MS Learn sample bundles CI and CD into one pipeline (Build stage → Deploy stage, same YAML file), which builds once and deploys straight to the cluster. That seems fine for a sing
DeepCamp AI