Skip to content

Commit

Permalink
Minor text update on cluster/namespace scoping
Browse files Browse the repository at this point in the history
  • Loading branch information
@gnunn1
gnunn1 committed Oct 17, 2024
1 parent 0e7d60e commit 47c18b9
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions content/modules/ROOT/pages/02-workshop-overview.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 47c18b9

Please sign in to comment.