#deployment

Implement GitOps workflow using ArgoCD. Setup: 1. Install ArgoCD on Kubernetes cluster. 2. Connect Git repository as source of truth. 3. Create Application manifests for each microservice. 4. Configure automated sync policies. 5. Set up health checks and sync waves. 6. Implement progressive delivery with Argo Rollouts (canary, blue-green). 7. RBAC for team access control. Use separate repos for app code and manifests. Include rollback procedures and disaster recovery plan.

Create production-ready Kubernetes manifests for a microservice. Resources: 1. Deployment with rolling update strategy and resource limits. 2. Service (ClusterIP) for internal communication. 3. Ingress with TLS termination. 4. ConfigMap for environment variables. 5. Secret for sensitive data. 6. HorizontalPodAutoscaler for auto-scaling. 7. PodDisruptionBudget for availability. Use namespaces, labels, and health checks (liveness/readiness probes). Include Helm chart structure for templating.

Implement zero-downtime deployments with Kubernetes. Setup: 1. Create blue and green deployment manifests with identical specs. 2. Configure service selector to route traffic between environments. 3. Implement health checks and readiness probes. 4. Set up Helm charts for version management. 5. Create CI/CD pipeline with automated testing gates. 6. Add rollback mechanism with previous version retention. 7. Implement traffic splitting for canary testing. 8. Monitor deployment metrics with Prometheus and Grafana. Include namespace isolation and resource quotas.

Containerize applications with Docker. Best practices: 1. Small base images (Alpine). 2. Multi-stage builds. 3. Layer caching optimization. 4. .dockerignore file. 5. Non-root user for security. 6. Health checks. 7. Environment-specific configs. 8. Volume mounts for data. Keep images lean. One process per container. Use docker-compose for local development. Tag images properly.

Implement safe feature releases using feature flags. Flag types: 1. Release flags: control feature deployment (temporary). 2. Experiment flags: A/B testing (temporary). 3. Ops flags: circuit breakers for performance (permanent). 4. Permission flags: user role access (permanent). Rollout strategy: 1. Internal team (0.1% traffic): validate basic functionality. 2. Beta users (1% traffic): gather feedback from friendly customers. 3. Gradual rollout (5%, 25%, 50%, 100%): monitor metrics at each stage. 4. Success criteria: error rates <0.1%, performance impact <10ms, user feedback positive. Monitoring: set up alerts for error spikes, performance regression, customer complaints. Rollback plan: instant flag toggle if issues detected. Tools: LaunchDarkly, Split, Unleash, or custom solution. Flag hygiene: remove old flags after full rollout, document flag purpose and owner.

Set up effective CI/CD pipeline. Stages: 1. Source (code commit triggers pipeline). 2. Build (compile, dependency installation). 3. Test (unit, integration, e2e tests). 4. Code Quality (linting, code coverage, SonarQube). 5. Security Scan (dependency vulnerabilities, SAST). 6. Deploy to Staging (automated). 7. Deploy to Production (manual approval or automated). Tools: GitHub Actions, GitLab CI, Jenkins, CircleCI. Use Docker for consistent environments. Parallel jobs for speed. Fail fast. Notifications on failure. Blue-green or canary deployments. Infrastructure as Code (Terraform). Measure: deployment frequency, lead time, MTTR.