AWS EKS GitOps Setup ₹500/task
Budget: ₹1,500 – ₹12,500 INR
I want to harden and modernise an existing Amazon EKS cluster, tackling each piece of work as a standalone task worth ₹ 500. You will receive limited but sufficient IAM permissions on the cluster and the linked AWS account.
Here is the exact work I need completed, one task at a time (I will test and release payment after each successful merge to the main branch and deployment via Argo CD):
1. Install Argo CD on the current EKS cluster and wire it to my Git repository so every subsequent change is fully GitOps-driven.
2. Enable Bitnami Sealed Secrets (or a comparable controller) so every application secret is encrypted at rest and in Git.
3. On-board our first service, LitDraft, to Argo CD and supply reusable Helm/Kustomize templates that make it easy for me to add the remaining 8–9 micro-services.
4. Stand up Prometheus and Grafana dashboards, exposing key metrics for the cluster, nodes and workloads.
5. Switch worker nodes to Spot Instances where possible and configure the appropriate auto-scaling rules to keep both resilience and cost optimisation in balance.
6. Produce concise runbooks and deployment docs so the internal team can operate everything without your involvement.
Acceptance for each task: manifest files live in the specified Git repo, the change deploys cleanly via Argo CD, and a quick screen-share or recorded demo shows the result working in the EKS environment.
If you are comfortable with AWS, kubectl, Helm/Kustomize, Prometheus, Grafana and have a track record of GitOps deployments, this will be quick, clean work. I am ready to start as soon as you can.
Here is the exact work I need completed, one task at a time (I will test and release payment after each successful merge to the main branch and deployment via Argo CD):
1. Install Argo CD on the current EKS cluster and wire it to my Git repository so every subsequent change is fully GitOps-driven.
2. Enable Bitnami Sealed Secrets (or a comparable controller) so every application secret is encrypted at rest and in Git.
3. On-board our first service, LitDraft, to Argo CD and supply reusable Helm/Kustomize templates that make it easy for me to add the remaining 8–9 micro-services.
4. Stand up Prometheus and Grafana dashboards, exposing key metrics for the cluster, nodes and workloads.
5. Switch worker nodes to Spot Instances where possible and configure the appropriate auto-scaling rules to keep both resilience and cost optimisation in balance.
6. Produce concise runbooks and deployment docs so the internal team can operate everything without your involvement.
Acceptance for each task: manifest files live in the specified Git repo, the change deploys cleanly via Argo CD, and a quick screen-share or recorded demo shows the result working in the EKS environment.
If you are comfortable with AWS, kubectl, Helm/Kustomize, Prometheus, Grafana and have a track record of GitOps deployments, this will be quick, clean work. I am ready to start as soon as you can.
Related categories:
PHP
System Admin
Linux
Cloud Computing
Amazon Web Services
Kubernetes
DevOps
Microservices