Azure AKS CI/CD, Auto Scaling apps hosted in Azure

Job ID: 40278047

Budget: ₹750 – ₹1,250 INR

I’m ready to move several enterprise-grade SaaS products (React front-ends, Node.js APIs, Postgres databases) into our own Azure tenancy and need the entire release flow automated. Every service will live in Docker containers and run on AKS; blue/green or canary style rollouts are essential so that a new push never impacts the live user base.

GitHub Actions will be the single source of truth for the CI/CD pipelines. I need jobs that:

• build and test the React and Node repos
• package images, push them to Azure Container Registry
• run schema-versioned database migrations before or during rollout
• deploy to AKS with zero-downtime strategies and automatic rollback on failure

Within the cluster, autoscaling must be tuned for CPU, memory, and HTTP load, fronted by an Azure Load Balancer or Ingress Controller. Connection pooling for Postgres should be handled cleanly—pgBouncer or a similar approach is fine as long as it keeps latency low and prevents runaway connections.

Security matters just as much as uptime. Private endpoints or an Azure VPN need to fence off internal APIs while still allowing public traffic through controlled ingress rules. Secrets must stay in Azure Key Vault, referenced only at deployment time.

Acceptance criteria
• A working GitHub Actions workflow file per service that can stand up a fresh environment from scratch
• Kubernetes manifests or Helm charts committed to repo and parameterized for dev, staging, and prod
• Demonstrated blue/green switch without dropping active sessions
• Autoscaling proof (metrics dashboards in Azure Monitor)
• Clear README or run-book so the in-house team can extend the pipelines unaided

Only serious proposals - start with aks when you apply automated or bot will be ignored.

If this end-to-end setup sounds well within your wheelhouse, I’m looking forward to your plan of attack and an estimated timeline.

We also need scripted env setup - like Dev, Staging, Prod so rollout must be smooth.