From 47c18b9c8e1a5de20597b1555e1882ffa263b318 Mon Sep 17 00:00:00 2001 From: Gerald Nunn Date: Thu, 17 Oct 2024 15:50:32 -0700 Subject: [PATCH] Minor text update on cluster/namespace scoping --- content/modules/ROOT/pages/02-workshop-overview.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/modules/ROOT/pages/02-workshop-overview.adoc b/content/modules/ROOT/pages/02-workshop-overview.adoc index 351e78e..759ad46 100644 --- a/content/modules/ROOT/pages/02-workshop-overview.adoc +++ b/content/modules/ROOT/pages/02-workshop-overview.adoc @@ -39,8 +39,9 @@ metadata: [NOTE] Argo Rollouts can be deployed as either a namespace or cluster scope. It has been provisioned here as cluster -scoped which is the default, namespace scope can be selected by setting `.spec.namespaceScoped: true`. NOTE -that only one cluster scoped instance of RolloutManager can exist on a cluster. +scoped which is the default, namespace scope can be selected by setting `.spec.namespaceScoped: true`. Keep in mind +that only one cluster scoped instance of RolloutManager can exist on a cluster. Also cluster scoped +and namespace scoped instances are not permitted on the same cluster. As shown above this is a simple declaration which in turn results in the Operator creating a deployment with the Argo Rollout controller monitoring all namespaces on the cluster for