# argocd Argo CD is a declarative GitOps continuous delivery tool for Kubernetes. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Using ArgoCD to Manage AI Model Deployments with GitOps DevFeed: [Using ArgoCD to Manage AI Model Deployments with GitOps]() Original publisher: [Read original article]() Author: Pramodh Kumar M Published: 2026-07-28T18:24:57Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [GitOps](), [argocd](), [model-deployment](), [Artificial Intelligence](), [model-serving](), [Architecture & Design]() Tags: [ai](), [ai-models](), [argo-rollouts-model-promotion](), [argocd](), [argocd-ai-model-deployment](), [argocd-applicationset](), [argocd-sync-waves](), [automation](), [ci-cd](), [declarative-model-serving](), [deployment](), [devops](), [gitops](), [gitops-for-ai-model-deployments](), [gitops-mlops](), [kserve](), [kserve-canary-deployment](), [kubernetes](), [kubernetes-model-deployment-rollback](), [ml-model-deployment](), [ml-model-versioning](), [mlops](), [model-deployment](), [model-registry-to-git-automation](), [model-serving](), [pull-requests](), [standard](), [tutorial]() ### AI overview This tutorial explains how to use ArgoCD and GitOps to deploy AI models while accounting for model weights stored outside container images. It covers pinned model references, rollback and recovery, synchronization ordering, readiness probes, evaluation-based promotion gates, and KServe status handling. ### Source excerpt Your microservices deploy through pull requests with full audit trails. Your models deploy because someone ran a script. Here is how to close that gap with ArgoCD, and what changes when the artifact weighs four gigabytes. ## Orchestration powered by Temporal at Zscaler: Wrap, don't rewrite DevFeed: [Orchestration powered by Temporal at Zscaler: Wrap, don't rewrite]() Original publisher: [Read original article]() Author: Abhishek Mitra Published: 2026-07-22T00:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [Orchestration](), [Automation](), [Ansible](), [opentofu](), [Terraform](), [argocd](), [GitOps](), [Provisioning]() Tags: [ansible](), [automation](), [aws-cloudformation](), [bash](), [ci](), [cli](), [gitops](), [infrastructure-as-code](), [orchestration](), [provisioning](), [temporal-voices]() ### AI overview The article describes how Zscaler designed a durable orchestration contract above eight heterogeneous automation engines, including Ansible, Terraform, OpenTofu, Helm, ArgoCD, Crossplane, Kubernetes Cluster API, AWS CloudFormation, and Jenkins. The approach aims to coordinate existing tools without rewriting them. ### Source excerpt How one durable contract above eight automation engines changed Zscaler's architecture without changing the engines ## Keycloak Community Survey Finds Demand for Official Helm Charts and More Robust GitOps Flows DevFeed: [Keycloak Community Survey Finds Demand for Official Helm Charts and More Robust GitOps Flows]() Original publisher: [Read original article]() Author: Keycloak Cloud Native team Published: 2026-03-18T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Helm charts](), [argocd](), [GitOps](), [configuration]() Tags: [adoption](), [argocd](), [challenges](), [community](), [configuration](), [containerized](), [deployments](), [gitops](), [helm-charts](), [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [results](), [saml](), [sso](), [survey]() ### AI overview Keycloak's survey of more than 360 respondents examined how the community deploys and manages Keycloak. Respondents expressed demand for official Helm Charts and more robust GitOps workflows, while adoption of the Keycloak Operator was reported as low because its setup is difficult to understand and its functionality is perceived as insufficient. ### Source excerpt Earlier this year, we conducted a survey to better understand how the community deploys and manages Keycloak in the real world. With over 360 respondents (!!), the results provide a better understanding of the community's needs and wishes. What we learned The survey results highlight a community that is deeply invested in the containerized ecosystem but is facing specific challenges in day-to-day operations. Key Findings: The Helm Charts: A significant portion of the community explicitly requested official Helm Charts, particularly for managing Keycloak installation and managing deployments via tools like ArgoCD. Operator: Adoption of the Keycloak Operator is not very high in the community, which is mainly caused by the fact that the Operator setup is hard to grasp, and do not provide the required functionality. GitOps & Configuration: There is a strong desire for more robust GitOps flows, especially when it comes to managing Keycloak resources like Realms and Clients. The whole Keycloak team is aware of these results and is discussing the next steps. Thank you to everyone who shared their feedback in this survey! More details: You can browse the detailed breakdown of the survey results in the slides below: ## Single-Node Kubernetes GitOps on a Budget DevFeed: [Single-Node Kubernetes GitOps on a Budget]() Original publisher: [Read original article]() Published: 2026-03-04T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [GitOps](), [k3s](), [argocd](), [Kubernetes](), [Deployment](), [Self-hosted](), [Firewall](), [TLS (Transport Layer Security)](), [traefik](), [Ubuntu](), [GitHub](), [Digital Ocean]() Tags: [argocd](), [deployment](), [digitalocean](), [firewall](), [github](), [gitops](), [k3s](), [kubernetes](), [lets](), [linux](), [macos](), [self-hosted]() ### AI overview This tutorial describes a budget-conscious, single-node Kubernetes platform built with k3s and GitOps. It covers bootstrapping an Ubuntu VM, syncing applications with ArgoCD, and adding TLS and firewall controls. The supplied text is truncated before the full implementation is presented. ### Source excerpt . [Single-Node Kubernetes GitOps on a Budget](single-node-k3s-gitops-on-a-budget-cover... ## How Wise bootstraps Spinnaker using ArgoCD DevFeed: [How Wise bootstraps Spinnaker using ArgoCD]() Original publisher: [Read original article]() Author: Nick Platt Published: 2023-02-20T12:24:46Z Content type: tutorial Language: en Sources: [Wise Engineering - Medium]() Topics: [argocd](), [spinnaker](), [CI/CD](), [GitOps](), [Kubernetes](), [Microservice](), [Deployment](), [Helm charts](), [Java]() Tags: [argo-cd](), [argocd](), [ci-cd](), [continuous-delivery](), [deployment](), [gitops](), [helm-charts](), [kubernetes](), [microservices](), [platform](), [spinnaker]() ### AI overview Wise explains how it bootstrapped Spinnaker automatically with ArgoCD instead of using a staging Spinnaker to manage production. The article compares Spinnaker's pipeline-based deployment model with ArgoCD's declarative GitOps reconciliation model and describes using ArgoCD and its App of Apps pattern to manage Spinnaker installations across Kubernetes clusters. ### Source excerpt Spinnaker and ArgoCD logos Deploying your deployment tool In our 2 part series, we discussed the state of our CI/CD systems and wrapped up with our vision for CD at Wise, and why we chose Spinnaker. Here's how we set up Spinnaker from scratch, overcoming the technical challenges of bootstrapping a CD platform. We wanted a hands-off and automated way to bootstrap Spinnaker. When researching across industry peers, one approach was to use a staging instance of Spinnaker to manage your production instance. This method of dual Spinnakers, wasn't viable for Wise, due to security concerns with a staging tool having access to change a production environment. It also meant accepting a potentially manual error prone process when managing your staging setup. Instead, we wanted to achieve a fully automatic installation for both of our Spinnaker environments and settled on using ArgoCD. Spinnaker & ArgoCD Spinnaker consists of around 11 Java microservices, which operates on a centralised deployment model -- push based deployments. It utilises pipelines heavily as its deployment strategy, which can be triggered via various input methods e.g. manual, artefact upload etc. Implementing deployments as pipelines allows engineers to describe a release as a set of steps, with powerful concepts such as canary analysis and quality gates built in. This is attractive for Wise, as use of standardised and reusable templates can enforce end consumers to follow a particular paved road e.g. canary deployments with automatic rollbacks. ArgoCD describes itself as "declarative GitOps for Kubernetes". It comprises fewer golang microservices and can be configured to be either centralised or decentralised. By default, ArgoCD differs by not utilising pipeline based deployments, instead operating via a GitOps reconciliation loop as its source of truth. Whatever is defined in Git, ArgoCD will try to reconcile within the cluster. ArgoCD is Kubernetes native and therefore can't be used for deploying infrast ## Deployment previews on Kubernetes DevFeed: [Deployment previews on Kubernetes]() Original publisher: [Read original article]() Author: Andreas Gounaris Published: 2022-11-11T07:30:00Z Content type: tutorial Language: en Sources: [Blueground Engineering blog]() Topics: [Kubernetes](), [Deployment](), [GitOps](), [argocd](), [Microservice](), [Netlify](), [Vercel]() Tags: [argocd](), [cost](), [deployment](), [developer-experience](), [devops](), [energy](), [gitops](), [kubernetes](), [netlify](), [self-service](), [services](), [vercel]() ### AI overview Blueground describes how it brought deployment previews to Kubernetes-hosted microservices using GitOps and ArgoCD. The approach replaced scarce static pre-production environments with temporary, self-service previews using production images and de-identified production data. ### Source excerpt Deployment previews - made popular by platforms like Vercel and Netlify - are not commonplace in microservice architectures. At Blueground, we brought deployment previews to K8s using ArgoCD. Well, it turned out to be so good, it is worth sharing.