Running Argo CD across 5 clusters and 500 clusters creates very different architecture decisions. ๐
Centralized, per-cluster, hybrid, or agent-based?
Our refreshed guide breaks down the models and their trade-offs: buff.ly/QjBPpmD

Running Argo CD across 5 clusters and 500 clusters creates very different architecture decisions. ๐
Centralized, per-cluster, hybrid, or agent-based?
Our refreshed guide breaks down the models and their trade-offs: buff.ly/QjBPpmD
Your promotion process may be scattered across CI jobs, scripts, PRs, and manual approvals. ๐
See how Kargo brings promotion, verification, governance, and audit history into one control plane: buff.ly/6cHY7DZ
Portainer 2.45.0 LTS porta numerose novitร per la gestione di Docker, Kubernetes, GitOps ed Edge Compute, con particolare attenzione alla sicurezza. #Portainer #Docker #Kubernetes #Linux #DevOps #GitOps www.linuxeasy.org/portainer-2-...
#ArgoCD #GitOps #Kubernetes
Using a GitOps approach with ArgoCD for your apps running in Kubernetes works well. Seeing examples of setting things up helps me understand them more. The example below installs ArgoCD with Helm and then deploys two apps.
One app comes from a
Argo Rollouts and Kargo automated rollbacks operate at different layers.
Argo Rollouts โ workload + traffic
Kargo โ Stage-level recovery across apps, config + infrastructure
See how they work together: buff.ly/sMOW8yC
GitOpsใฎใใซใใฏใฉในใฟ้็จใซRancher Fleetใ้ธใถ็็ฑ๏ฝArgo CDๆฏ่ผใจAIๆไปฃใฎ่จญ่จ
Should #Terraform-generated deployment config live outside Git?
One approach keeps the handoff Git-based:
๐ง๐ฒ๐ฟ๐ฟ๐ฎ๐ณ๐ผ๐ฟ๐บ โ ๐ฏ๐ฟ๐ฎ๐ป๐ฐ๐ต โ ๐ฐ๐ผ๐ป๐ณ๐ถ๐ด โ ๐ฃ๐ฅ โ ๐บ๐ฒ๐ฟ๐ด๐ฒ โ ๐๐ฟ๐ด๐ผ ๐๐ ๐
See the implementation + trade-offs: buff.ly/pScJ1zv
GitOps shouldnโt replace manual deployments with a ticket queue.
On Sept. 22 in Barcelona, Emburse shares how its platform team moved toward developer self-service as its Argo CD environment scaled. ๐
๐ buff.ly/iugvVGv
#EKS #Kubernetes #AWS #PlatformEngineering #GitOps
Setting up an Ingress on a new Kubernetes cluster on AWS using the Elastic Kubernetes Service (EKS) can be confusing to some.
Github repo is just a quick copy, there is some configuration required, some env variables in code, digests and few steps on AWS all documented.
AWS lab deployment is then fully scripted, it costs about 5โฌ/day
github.com/invertedmush...
#GitOps #AWS #IaC #CI/CD
CMMS the hard way: contract-first APIs, transactional outbox, hash-chained audit, offline Android field client with a Rust encrypted core, GitOps to Kubernetes, disposable AWS lab via Pulumi.
#TypeScript #NestJS #Rust #Android #Kubernetes #GitOps
github.com/invertedmush...
Two gotchas to cap server-side: stale status (reconcile = 3 min, expose reconciledAt) and runaway rollback loops โ one rollback per app per hour.
Full build:
https://devtocash.com/blog/2026-08-25-argocd-mcp-server-gitops-ai-agents
"From Manual Deployments to GitOps: How Argo CD Changes Kubernetes Delivery" by Shubham Wadkar