11-11, 16:30–17:00 (MST), Theater
In the Kubernetes-native ecosystem, GitOps is the go-to approach for deploying applications, with ArgoCD leading the charge by syncing Git repositories with Kubernetes clusters. However, while ArgoCD excels at maintaining deployment consistency, it may not suffice as a standalone continuous deployment (CD) tool. This discussion explores ArgoCD’s limitations, including gaps in security checks, automated rollouts, SLO based rollbacks, and support for advanced branching strategies, questioning whether it can truly be considered a silver bullet or if it should be part of a broader GitOps CD strategy.
In the Kubernetes environment, GitOps is a popular way to deploy applications, with ArgoCD being a key tool to keep everything in sync between Git and Kubernetes clusters. However, while ArgoCD works well for ensuring deployments match what’s in Git, it might not be enough on its own for a complete continuous deployment (CD) pipeline. This discussion will highlight some of ArgoCD’s limitations and consider whether it should be used alongside other tools in a broader CD strategy or ArgoCD standalone is enough.
A Kubernetes head with a travelling soul, Abhinav is deeply committed to open-source software and cloud-native technologies. As a Solution Architect at Devtron Inc., he manages cloud-based application deployments and actively contributes to the open-source Devtron project.
As a CNCF Ambassador, Abhinav is on a mission to make Kubernetes adoption as easy as packing for a weekend getaway, sharing his experience and knowledge just like his travel stories.