Skip to content

Commit be36224

Browse files
committed
Blog post for singleArgoCD
1 parent f4dc7b4 commit be36224

1 file changed

Lines changed: 45 additions & 0 deletions

File tree

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
date: 2026-06-04
3+
title: New option to use a single ArgoCD instance
4+
summary: The Validated Patterns framework now supports a global.singleArgoCD flag that consolidates all group applications into a single ArgoCD instance
5+
author: Michele Baldessari
6+
blog_tags:
7+
- patterns
8+
- argocd
9+
- gitops
10+
- acm
11+
---
12+
:toc:
13+
:imagesdir: /images
14+
15+
== Preamble
16+
17+
Historically, the VP framework had two Argo CD instances: a clusterwide one used for
18+
more privileged parts like namespaces, subscriptions, etc. where the "App-of-Apps" Argo
19+
application lived and another namespaced Argo CD instance where all the other
20+
Argo Applications lived.
21+
22+
While this separation provided useful security boundaries, it brought additional resource
23+
usage and complexity. Running a single instance reduces the overall footprint on the cluster
24+
and simplifies troubleshooting by having all Argo Applications in one place.
25+
26+
== How to have a single Argo CD instance
27+
28+
It is now possible to use a single Argo CD instance for all objects managed by
29+
the Validated Patterns framework.
30+
31+
Set `.Values.global.singleArgoCD` to `true` in your pattern's `values-global.yaml` file:
32+
33+
[source,yaml]
34+
----
35+
global:
36+
pattern: multicloud-gitops
37+
singleArgoCD: true
38+
----
39+
40+
No other changes are needed. The clustergroup charts and the ACM chart will handle
41+
everything. The "App-of-Apps" pattern stays the same only the target Argo CD instance changes.
42+
43+
Note that this flag is only supported for new installs. Changing an existing installation
44+
with two Argo CD instances by setting `.Values.global.singleArgoCD` to true afterwards
45+
is very unlikely to work.

0 commit comments

Comments
 (0)