Argo CD handles delivery. What about moving apps from dev โ staging โ production? ๐
Join Kargo Maintainer Taylor Thomas for GitOps 101 and learn how Kargo brings automation and structure to promotions.
Register: buff.ly/O1kBjZP

Argo CD handles delivery. What about moving apps from dev โ staging โ production? ๐
Join Kargo Maintainer Taylor Thomas for GitOps 101 and learn how Kargo brings automation and structure to promotions.
Register: buff.ly/O1kBjZP
dev.to/aws-builders/argo-cd-app-of-apps-on-eks-bcc #aws #EKS #ArgoCD #GitOps Managing multiple apps across Kubernetes clusters can get complicated. Using a Gitops approach with ArgoCD and using The "App of Apps" pattern offers a clean way to bootstrap everything.
Your CI runner is a security hole. Push-based CD means Jenkins holds prod kubeconfig and shoves YAML blindly. Pull-based ArgoCD reconciliation https://www.valtersit.com/guides/gitlab/gitops_and_argocd-why_you_should_stop_pushing_your_deployments/ #gitops #argocd #kubernetes
Barcelona next week: Emburse + Akuity on scaling Argo CD, developer self-service, and managing promotion across environments with Kargo. ๐
Plus a hands-on deployment session. ๐
โก๏ธ buff.ly/iK0WH7K
#ArgoCD #GitOps #Kubernetes #PlatformEngineering
Using a GitOps approach for managing apps in Kubernetes helps with organization and maintainability.
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
#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ๆไปฃใฎ่จญ่จ
I just published Argo Rollouts: Progressive Delivery for GitOps Practitioners Is Now Available medium.com/curious-devs...
You can find the ebook here, with an early bird code: curiousdevscorner.gumroad.com/l/argo-rollo...
#devops #argorollouts #argocd #kubernetes
Should #Terraform-generated deployment config live outside Git?
One approach keeps the handoff Git-based:
๐ง๐ฒ๐ฟ๐ฟ๐ฎ๐ณ๐ผ๐ฟ๐บ โ ๐ฏ๐ฟ๐ฎ๐ป๐ฐ๐ต โ ๐ฐ๐ผ๐ป๐ณ๐ถ๐ด โ ๐ฃ๐ฅ โ ๐บ๐ฒ๐ฟ๐ด๐ฒ โ ๐๐ฟ๐ด๐ผ ๐๐ ๐
See the implementation + trade-offs: buff.ly/pScJ1zv
#Kubernetes #Minikube #EKS #Karpenter #ArgoCD
Many Kubernetes tutorials stay at the high level, which is understandable given how much ground there is to cover. The article below goes into more detail, taking you from a fresh Minikube install through a working GitOps loop
Managing #Kubernetes across clouds gets complicated when Argo CD needs direct access to every cluster.
See how an outbound agent model removes the need for VPNs, VPC peering, or exposed API servers. ๐
๐ buff.ly/ueaO2Hl
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
๐ Happening TODAY in Shanghai!
If you are attending KubeCon + CloudNativeCon + OpenInfra Summit + PyTorch Conference China 2026, do not miss our tech session on the future of DevOps and autonomous infrastructure!! @kevindubois.com
4:15 pm at Mandarin Hall I
#AgenticAI #ArgoCD #IBM
Synced โ Healthy
Your Git state and cluster state can match perfectly while the application itself is broken.
I walked through why these are two separate signals and what Argo CD is actually telling us.
youtu.be/EFjIM3TmhXQ
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