Ongoing DevOps Support & Mentorship
Budget: ₹12,500 – ₹37,500 INR
I need hands-on help keeping a complex DevOps stack running smoothly day-to-day. The focus is threefold:
• CI/CD pipeline tuning and troubleshooting
• Building and refining Infrastructure-as-Code
• Tightening Monitoring & Logging so issues surface early
My environment is container-centric, so you’ll work with Docker for image management and Kubernetes for orchestration. Provisioning happens through Terraform, while configuration tasks lean on Ansible; most glue scripts are in Python.
Expect to jump on screen-sharing calls, pair through problems in real time, and then commit clean, working YAML/HCL/Playbook code back to the repo with concise comments. Each session should finish with a brief summary of what changed and any follow-up tasks so I can track progress easily.
Deliverables per engagement
1. Working pipeline or IaC change merged and green in the build.
2. Clear written recap (commands run, files touched, next steps).
3. If we touch monitoring, a validated alert or dashboard proving the new signal works.
Availability during my core hours (UTC-5 mornings) is important; otherwise the cadence and duration of support sessions are flexible. If you’re comfortable diving across this toolchain and explaining your thought process as we go, let’s get started.
• CI/CD pipeline tuning and troubleshooting
• Building and refining Infrastructure-as-Code
• Tightening Monitoring & Logging so issues surface early
My environment is container-centric, so you’ll work with Docker for image management and Kubernetes for orchestration. Provisioning happens through Terraform, while configuration tasks lean on Ansible; most glue scripts are in Python.
Expect to jump on screen-sharing calls, pair through problems in real time, and then commit clean, working YAML/HCL/Playbook code back to the repo with concise comments. Each session should finish with a brief summary of what changed and any follow-up tasks so I can track progress easily.
Deliverables per engagement
1. Working pipeline or IaC change merged and green in the build.
2. Clear written recap (commands run, files touched, next steps).
3. If we touch monitoring, a validated alert or dashboard proving the new signal works.
Availability during my core hours (UTC-5 mornings) is important; otherwise the cadence and duration of support sessions are flexible. If you’re comfortable diving across this toolchain and explaining your thought process as we go, let’s get started.