I configure ArgoCD or Flux for GitOps-based Kubernetes deployments — turning your cluster state into a Git-managed, continuously reconciled source of truth. Promoting to production becomes a Git merge; rollback becomes a Git revert.
Setup includes: ArgoCD or Flux installation on your cluster; app-of-apps structure or Kustomize overlays for multi-environment management; ApplicationSets or Flux image automation for fleet deployments; RBAC for team-scoped privs; Slack/etc notifications on sync events; and secret management integration via Sealed Secrets or External Secrets Operator pulling from AWS SSM, GCP Secret Manager, or HashiCorp Vault.
For multi-cluster setups I configure centralized management with environment promotion workflows. I also integrate with your existing CI pipeline so image builds automatically trigger GitOps sync.
Share your Kubernetes cluster privs, Git provider, current Helm charts or manifests, and target environments. I'll recommend ArgoCD vs Flux based on your team's needs if you're undecided.