Argo CD team is happy to announce the availability of a first candidate for the v2.1 release. The new release introduces several brand new features, bug fixes, and multiple enhancements of existing functionalities. Read on to learn more!
Argo CD is well known for its rich set of features that allows using it in a multi-tenant environment. Features like SSO, RBAC, built-in user management allow using the single Argo CD instance to serve the needs of multiple teams without compromising security.
However, not everyone needs multi-tenancy. What if you just want to use Argo CD yourself and just want to…
The Argoproj community has been working on notifications functionality for a while now. We’ve tried several different approaches and learned a lot from our early users. Based on our learnings, we’ve come up with the idea of a notifications engine that solves various notifications-related use cases for all Argo projects and even beyond.
The first notifications engine consumer was the argocd-notifications project that provides notifications for the Argo CD Application CRD and soon for Argo Rollouts as well. Today, we are happy to announce the first version of Notifications Engine 🎉 !
The Notifications Engine is a Golang based library…
Argo CD Notifications just got better. The Argoproj team is happy to announce the v1.1 release. Please keep reading to learn what’s new.
The MS Teams integration was still possible using generic Webhooks, but it didn’t provide the best user experience. This release introduces native MS Teams support. Instead of manually defining the MS Teams webhook payload template you can take just register MS Teams service by writing couple lines of YAML.
For convenience, the catalog of pre-configured message templates includes templates for MS Teams!
Thanks to Yuri Denysenko from Codefresh for implementing this feature! 👏
Argoproj team is proud to announce the first release candidate for Argo CD v2.0! As denoted by the version number, this is a major release with many new features and enhancements, but no breaking changes or painful migrations. So what is new?
Argo CD is a popular Kubernetes continuous deployment tool that enables GitOps workflow. The tool enables developers to manage infrastructure in the exact same way they manage application source code and provides powerful day-two features to monitor and manage applications in production.
Infrastructure as a code increases developers’ productivity and significantly reduces the number of errors, misconfigurations, and ultimately the number of incidents. The methodology works well, but it does require you to make a Git commit for each and every change. This becomes very annoying if you follow continuous deployment principles and deploy new changes multiple times a week…
One of the mains goals of Argo CD is to provide a great experience of automating day-to-day tasks that required to manage Kubernetes clusters. The GitOps functions, a convenient web and command-line interface make it the perfect tool for developers who deploy applications to Kubernetes. Besides developers, there are operators: members of the platform team who run Kubernetes clusters and tools like Argo CD for the whole organization. How about them?
Argo CD can help them too! Keep reading to learn which Argo CD features allow building a multi-tenant platform on top of a fleet of multi-tenant Kubernetes clusters.
Notifications are an important part of the complete end-user experience but can be tricky to get right. Different organizations use different kinds of notifications services such as Slack, OpsGenie, or just good old email. There are dozens of different types of events that may need notification, so it is hard to predict all possible scenarios and optimize for all of them. Finally, every organization has different standards and may want to customize notification in a different way.
The Argo CD v1.8 release is almost here. The team just published the first release candidate and is excited to share what’s new in this release!
As Argo CD adoption continues to grow, we have to keep pushing Argo CD scalability limits again and again. This is probably a never-ending quest, but the v1.8 release is a huge step forward. We have implemented improvements that enable a single Argo CD instance to comfortably manage thousands of applications across hundreds of clusters. This enables advanced use cases such as “cluster addons”, large mono-repositories, and opens the door for the ApplicationSet project…
Argo GitOps Engine is a library that implements core GitOps features such as resource diffing and the ability to use various synchronization strategies.
Originally used to power Argo CD, it was open-sourced by the Argo team to democratize GitOps. Their goal was to enable others to quickly build specialized tools that implement specific GitOps use cases, such as bootstrapping a Kubernetes cluster or decentralizing management of namespaces. The GitOps Engine was started as a partnership between Intuit and WeaveWorks and is now being driven by Intuit, Red Hat, and GitLab.
At GitLab, we took an interest in the GitOps Engine…
The first release candidate is available at https://github.com/argoproj/argo-cd/releases/tag/v1.7.0-rc1! This release introduces multiple enhancements to existing features, some brand new features, and a ton of bug fixes.
Every change to the Git repository that stores Kubernetes resource manifests usually goes through multiple automated checks. The checks ensure high levels of quality and security. The security checks can include verifying the identity of the committer via GnuPG signatures. As of v1.7, it is possible to configure ArgoCD to only sync against commits with a valid signature.
The list of public GPG keys required for verification is configured at the system level and…