The cloud-native landscape has witnessed a significant milestone with the release of Argo CD 3.0, bringing transformative improvements to GitOps workflows and addressing long-standing pain points in Kubernetes deployment management. In an exclusive interview at KubeCon London, two key maintainers of the project revealed how community feedback shaped this major release and what it means for the future of continuous delivery.

Addressing GitOps’ Biggest Challenge: Secret Management

Regina Voloshin, Argo CD maintainer and 3.0 release champion from Octopus Deploy, highlighted one of the most significant changes in this release: the project’s new opinionated stance on secret management. “Until today, we were kind of unopinionated, but now we have an opinion on that,” Voloshin explained during the KubeStruck interview.

The new approach recommends using Kubernetes operators such as Sealed Secrets operator or External Secrets operator, moving away from different plugins and automation to populate secrets during the Argo CD manifest generation phase. This shift addresses what has historically been one of the biggest pain points for teams implementing GitOps practices.

For organizations struggling with secure secret management in their GitOps workflows, this opinionated approach provides clear guidance and best practices, eliminating the guesswork that has plagued many implementations.

Performance and Scalability: The Foundation for Enterprise Adoption

Beyond security improvements, Argo CD 3.0 delivers substantial performance enhancements that directly impact enterprise scalability. The release focuses particularly on managing deployments across multiple clusters – a critical requirement for organizations operating at scale.

“Argo CD is becoming significantly more performant and scalable, which makes the application delivery process more efficient and reliable,” Voloshin noted. These improvements provide real-time insights into application status, transforming how platform teams monitor and manage their Kubernetes environments.

Ishita Sequeira, Senior Software Engineer at Red Hat and Argo CD maintainer, emphasized how these performance gains simplify the overall GitOps experience. The enhanced efficiency means platform teams can focus on strategic initiatives rather than wrestling with infrastructure complexity.

Fine-Grained RBAC: Security Meets Usability

Version 3.0 introduces fine-grained Role-Based Access Control (RBAC), addressing enterprise security requirements while maintaining usability. “It’s now possible to implement fine-grained RBAC, which makes it easier for teams to define precisely which RBAC rules should be in place,” Sequeira explained.

This enhancement is particularly valuable for organizations with complex security requirements and multiple teams accessing the same cloud-native infrastructure. The granular control allows security teams to implement precise access policies while enabling development teams to maintain their velocity.

Multi-Cluster Support: Simplifying Global Operations

The enhanced multi-cluster support in Argo CD 3.0 represents a significant step forward for platform teams managing global environments. The improved performance and scalability directly translate to simplified multi-cluster management, reducing the operational overhead that has traditionally been associated with large-scale Kubernetes deployments.

“Platform teams won’t need to know as much about configuring Argo CD performance, which will make things much easier,” Voloshin explained. This simplification is crucial for organizations operating across multiple regions and environments, where complexity can quickly become unmanageable.

Community-Driven Development: The Open Source Advantage

The development of Argo CD 3.0 exemplifies the power of community-driven open source projects. The maintainers actively sought feedback through blog posts, CNCF Slack channels, and direct community engagement to understand pain points and desired improvements.

“The community’s feedback was truly invaluable—it not only helped us shape this release, but also allowed us to incorporate the many lessons and best practices the community had learned,” Voloshin shared.

This collaborative approach ensures that the project evolves based on real-world usage patterns and requirements, rather than theoretical assumptions about user needs.

Looking Ahead: The Future of GitOps

With version 3.0 establishing a solid foundation through deprecated API removal and architectural improvements, the Argo CD team is already planning the next phase of development. Upcoming features include automated pull request diffs for internal developer platforms, environment promotion capabilities, and extended support for generated manifest patterns.

These roadmap items suggest a continued focus on simplifying complex workflows while providing the advanced capabilities that enterprise environments require.

The Broader Impact on Cloud-Native Adoption

Argo CD 3.0’s improvements align with broader trends in cloud-native adoption, where organizations are seeking solutions that reduce complexity while increasing reliability and security. The opinionated approach to secret management, combined with performance improvements and enhanced RBAC, positions Argo CD as a more mature and enterprise-ready solution.

For organizations evaluating GitOps tools or considering upgrades to their existing continuous delivery infrastructure, Argo CD 3.0 represents a significant milestone that addresses many of the practical challenges that have hindered widespread adoption.

The release demonstrates how successful open source projects evolve by listening to their communities, implementing feedback systematically, and maintaining a clear vision for solving real-world problems. As GitOps continues to mature as a discipline, releases like Argo CD 3.0 help establish the standards and best practices that will define the next generation of software delivery.

For more insights on cloud-native technologies and open source projects, visit TFiR for exclusive interviews and analysis from industry leaders.

Interview Transcript

Show: KubeStruck
Host: Swapnil Bhartiya
Guests: Regina Voloshin, Argo CD Maintainer and 3.0 Release Champion, Open Source Software Tech Lead at Octopus Deploy: Ishita Sequeira, Senior Software Engineer at Red Hat and Argo CD Maintainer

Swapnil Bhartiya: Hi, this is Swapnil Bhartiya, and we are here at KubeCon + CloudNativeCon in London. Today we have two awesome guests from the Argo CD project: Regina Voloshin, Argo CD maintainer and 3.0 release champion, and also Open Source Software Tech Lead at Octopus Deploy, and Ishita Sequeira, Senior Software Engineer at Red Hat and Argo CD maintainer. Ishita, Regina, it’s great to have you on the show.

Ishita Sequeira: Thanks. Thank you. It’s great to be here.

Swapnil Bhartiya: Can you quickly tell our audience what the Argo CD product is all about?

Regina Voloshin: So Argo CD comes into the picture when we’re talking about how we want to perform continuous delivery for applications in Kubernetes. Argo CD basically relies on developers interacting with Git to specify the configurations for their Kubernetes deployments in Git. Then Argo CD is basically used as an engine to synchronize those manifests in Git to the Kubernetes cluster, and it will also go and check whether something has changed in the cluster, and it will automatically reapply this single source of truth that is in Git. So it’s heavily based on the GitOps principle.

Swapnil Bhartiya: If you look at Kubernetes, what are the specific pain points that users face that Argo CD addresses?

Regina Voloshin: When we’re talking about software application delivery using GitOps, one of the biggest pain points that people have is related to managing secrets with GitOps. With this release, we’re actually now being opinionated on how users who work with GitOps should be handling secret management. Until today, we were kind of unopinionated, but now we have an opinion on that, and we recommend people to use Kubernetes operators such as Sealed Secrets operator or External Secrets operator, instead of using different plugins and automation to populate those secrets during the Argo CD manifest generation phase. So this is one pain point that Argo CD 3.0 is actually addressing.

Another pain point is performance and scalability, especially when people are managing deployments across multiple clusters. Now Argo CD is coming with much better performance and more scalability, and this makes the application delivery process more efficient and more reliable.

Ishita Sequeira: With version 3, it’s possible to have fine-grained RBAC, which makes it easier for folks to specify exactly what RBAC rules should be there. So yeah, fine-grained RBAC is one point which has been a part of version 3.

Swapnil Bhartiya: Can you also talk about how, with this release, businesses are looking at delivery and the impact on business itself?

Ishita Sequeira: Argo CD architecture is a crucial one for businesses, and making it easier for businesses to understand this architecture was the main thing we decided to focus on with version 3. We are trying to achieve that with this release.

Swapnil Bhartiya: Can you also talk about how this release fits into the much broader GitOps or cloud-native landscape?

Ishita Sequeira: It just becomes easier. With this release, it just becomes easier because we are aiming toward performance improvement. So with the performance improvement, it just becomes easier to have GitOps simplified.

Regina Voloshin: Yeah, I think it’s also going to be a lot easier for people to adopt GitOps, because, as already mentioned, GitOps secrets is something that is very crucial. Also, if we think about Argo CD, it powers both the deployments and the monitoring. With this release, since Argo CD is becoming more performant, we can allow users to have real-time insights about their application status.

Swapnil Bhartiya: This release has also added multi-cluster support. What does it mean for operations and platform teams when they are looking at global environments?

Regina Voloshin: I think what will happen with the multi-cluster support right now is that, because Argo CD becomes more performant and more scalable, it will be easier for platform teams to manage those multi-cluster environments. Also, they will not need to know so much about how to configure Argo CD performance, so it will be much easier for them, and it will be a much simpler task in terms of multi-cluster management.

Swapnil Bhartiya: Can you also talk about what role the community played to shape this release?

Ishita Sequeira: I think for version 3, we’ve tried to gain a lot of help from the community. We’ve posted blogs regarding how folks could help with version 3 and shape it in a better way. The way we tried to gain help from the community was by asking through the Slack channel, the CNCF Slack channel, which helped in understanding what could be improved and what are the pain points which they would want to have removed from version 3. So we’ve tried to consider them mostly. That’s how the community has helped a lot in making version 3 a better place.

Regina Voloshin: The community feedback was really invaluable. This feedback both helped us shape this release, and it also helped us to pack all those great lessons and best practices that the community learned into Argo CD version 3, so that now all users can benefit from that.

Swapnil Bhartiya: Now version 3 is out. So talk a bit about—no pun intended—what else is in your pipeline? When we look at GitOps or delivery, how is the whole landscape evolving?

Regina Voloshin: First of all, with version 3, we had the opportunity to remove some deprecated APIs, and this helps us streamline the development of Argo CD. This lays the groundwork for the next features that we want to work on during the next year. There is a full backlog of features. I think one of the things that is going to happen next is that in environments where we have internal developer platforms, those are going to benefit from automated pull request diffs.

Ishita Sequeira: And also there’ll be environment promotion, which will evolve in the next two years. So that’s also going to play a major role. The evolution will take—it’s going to be a slow process, but you could see that in the next two years. And also the one which Regina mentioned regarding the manifest—that’s also an important thing which will be coming up for Argo CD.

Regina Voloshin: Yes, extended support for the generated manifest pattern.

Swapnil Bhartiya: Regina, thank you so much for taking time out today and giving us an update on Argo CD and version 3—how the project is growing, how the project is maturing. Thanks for the great insights. As usual, I would love to have you folks back on the show to talk about future developments. Thank you.

Regina Voloshin: Thank you so much. I was really honored to be here today, and thank you so much for being such a great host.

Swapnil Bhartiya: The honor and pleasure are all mine. Thank you.

Ishita Sequeira: Thanks, Swapnil. Thanks for having us here. Thanks a lot.