Production Kubernetes Deployment Setup
Budget: $30 – $250 USD
Our containerised app is running smoothly in dev and it is time to put it live. I need someone who can take our current manifests, adapt them for the production Kubernetes cluster (the cluster is simply “Kubernetes”, not EKS, GKE or AKS), and guide the rollout during business hours without disrupting users.
The scope covers everything from tightening resource limits and secrets, through drafting the change-control request, to standing by while QA runs smoke tests in prod. You will document each step, build in an easy rollback, and leave us with clear Helm- or kubectl-ready artefacts checked into our repo.
Deliverables
• Production-ready manifests/Helm charts, committed and peer-reviewed
• Written CCR with step-by-step run-book for change approval
• Live deployment executed during the agreed window and monitored until QA gives the green light
• Rollback procedure proven on staging
Acceptance criteria
• All pods show Ready status for 30 min post-deployment
• QA smoke tests return expected 200/OK responses across services
• CCR and deployment guide reside in /ops with version history
We already use GitLab CI, Helm 3 and Argo Rollouts; familiarity will help but is not mandatory. Please tell me about comparable production migrations you’ve led and your availability to schedule the CCR with in 2 this mounth
The scope covers everything from tightening resource limits and secrets, through drafting the change-control request, to standing by while QA runs smoke tests in prod. You will document each step, build in an easy rollback, and leave us with clear Helm- or kubectl-ready artefacts checked into our repo.
Deliverables
• Production-ready manifests/Helm charts, committed and peer-reviewed
• Written CCR with step-by-step run-book for change approval
• Live deployment executed during the agreed window and monitored until QA gives the green light
• Rollback procedure proven on staging
Acceptance criteria
• All pods show Ready status for 30 min post-deployment
• QA smoke tests return expected 200/OK responses across services
• CCR and deployment guide reside in /ops with version history
We already use GitLab CI, Helm 3 and Argo Rollouts; familiarity will help but is not mandatory. Please tell me about comparable production migrations you’ve led and your availability to schedule the CCR with in 2 this mounth