Browse categories
Explore
Fiverr Pro
English
$
USD
I will set up gitops on kubernetes with argocd or flux
Secure, Scalable and Cloud Automated DevOps Solutions
I am a DevOps Engineer with 10 years of hands-on experience in a service-based IT company.
I have worked on enterprise-level applications and production environments.
My expertise includes:
✔ CI/CD p...
About this Gig
Still deploying manually? One bad script away from a 2 AM outage?
I implement production-grade GitOps on your Kubernetes cluster using ArgoCD or Flux CD so your Git repo becomes the single source of truth for every deployment.
Push a commit. Your cluster updates. Someone edits a live resource by hand. ArgoCD detects the drift and self-heals. Every change is auditable, every rollback is instant.
With 10+ years of Kubernetes and cloud infrastructure experience across EKS, GKE, and AKS, here's what I set up for you:
- ArgoCD or Flux CD install & config
- Drift detection & auto-sync policies
- Multi-env setup (dev / staging / prod)
- Sealed Secrets / External Secrets
- Helm + Kustomize overlay structure
- CI/CD handoff (GitHub Actions, GitLab)
- RBAC & SSO integration
- Slack / webhook deploy notifications
Works with any cluster cloud or bare-metal. Structured to fit your team size, branching model, and release cadence so it actually gets adopted.
Message me your current setup I'll reply with a clear plan and timeline.
Tools:
Kubernetes
•
Docker
•
Amazon EKS
•
Google Kubernetes Engine
Frameworks:
Npm
•
Terraform
•
Ansible
Programming language:
Bash
•
Java
•
Python
•
Ruby
•
Golang
Expertise:
Debugging
•
Development
•
Configuration
My Portfolio
Other DevOps Engineering Services I Offer
FAQ
What's your experience with ArgoCD and Flux specifically?
I've implemented GitOps pipelines with both ArgoCD and Flux CD across production environments on EKS, GKE, and AKS — including multi-cluster setups, App-of-Apps patterns, and Flux's multi-tenancy model. With 10+ years in Kubernetes and cloud infrastructure, I've seen what breaks in real teams and I
ArgoCD or Flux — which should I pick?
It depends on your team and workflow. ArgoCD gives you a powerful UI, intuitive visualisation of sync state, and strong RBAC — great for teams who want visibility. Flux is fully GitOps-native, lighter-weight, and better suited to multi-tenant and platform-engineering patterns. Tell me your setup in
Will this work with my existing CI pipeline?
Yes. GitOps separates CI (build, test, push image) from CD (deploy to cluster). I'll wire your existing pipeline — GitHub Actions, GitLab CI, CircleCI, Jenkins, or whatever you use — to update image tags or manifests in Git, which triggers the GitOps sync automatically. No CI rework required; it slo
What if something breaks after you deliver?
Every package includes a post-delivery support window (3, 5, or 20 days depending on tier) during which I fix any issues caused by the work I delivered — at no extra cost. I also do a live walkthrough of everything I've built, so your team isn't dependent on me to operate it.
Can you help with secrets management inside GitOps?
Absolutely — this is one of the most overlooked parts of a GitOps setup. I implement Sealed Secrets (encrypts secrets in Git) or External Secrets Operator (syncs from AWS Secrets Manager, Vault, GCP Secret Manager) depending on what you already use. You get secrets handled securely without storing p
Do you support multi-cluster GitOps?
Yes — covered in the Enterprise package. I set up a hub-spoke model (one ArgoCD instance managing multiple target clusters) or a distributed Flux setup where each cluster pulls from a shared or tenant-specific Git source. This is common for platform teams managing staging, prod, and regional cluster
Can you set up canary or blue-green deployments too?
Yes — that's Progressive Delivery, and it's included in the Enterprise package. I implement Argo Rollouts or Flagger with your choice of traffic splitting (Nginx, Istio, Linkerd, or AWS ALB). Deployments roll out gradually, monitor your metrics (Prometheus, Datadog), and automatically roll back if e
