diff --git a/content/blog/2026-06-04-single-argocd-option.adoc b/content/blog/2026-06-04-single-argocd-option.adoc
new file mode 100644
index 000000000..23d758e4e
--- /dev/null
+++ b/content/blog/2026-06-04-single-argocd-option.adoc
@@ -0,0 +1,45 @@
+---
+ date: 2026-06-04
+ title: New option to use a single ArgoCD instance
+ summary: The Validated Patterns framework now supports a global.singleArgoCD flag that consolidates all group applications into a single ArgoCD instance
+ author: Michele Baldessari
+ blog_tags:
+ - patterns
+ - argocd
+ - gitops
+ - acm
+---
+:toc:
+:imagesdir: /images
+
+== Preamble
+
+Historically, the VP framework had two Argo CD instances: a clusterwide one used for
+more privileged parts like namespaces, subscriptions, etc. where the "App-of-Apps" Argo
+application lived and another namespaced Argo CD instance where all the other
+Argo Applications lived. 
+
+While this separation provided useful security boundaries, it brought additional resource
+usage and complexity. Running a single instance reduces the overall footprint on the cluster
+and simplifies troubleshooting by having all Argo Applications in one place.
+
+== How to have a single Argo CD instance
+
+It is now possible to use a single Argo CD instance for all objects managed by
+the Validated Patterns framework.
+
+Set `.Values.global.singleArgoCD` to `true` in your pattern's `values-global.yaml` file:
+
+[source,yaml]
+----
+global:
+  pattern: multicloud-gitops
+  singleArgoCD: true
+----
+
+No other changes are needed. The clustergroup charts and the ACM chart will handle
+everything. The "App-of-Apps" pattern stays the same only the target Argo CD instance changes.
+
+Note that this flag is only supported for new installs. Changing an existing installation
+with two Argo CD instances by setting `.Values.global.singleArgoCD` to true afterwards
+is very unlikely to work.