Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document how to configure cluster-scoped ArgoCD instances #350

Merged
merged 2 commits into from
Aug 12, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions docs/modules/ROOT/pages/how-tos/gitops/cluster-scope-argocd.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
= Configure an ArgoCD instance to be cluster-scoped

== Prerequisites

* Access to tenant repository
* Knowledge of the namespace in which the cluster-scoped ArgoCD shall be deployed

== Configure ArgoCD component

. Add the following configuration to the cluster's config file in the tenant repository:
+
[source,yaml]
--
argocd:
operator:
cluster_scope_namespaces:
- [NAMESPACE NAME]
--

. Commit your change and create a pull request.

. After merge, wait for the catalog to be compiled.

. Inform the customer that they may now deploy their ArgoCD instance as per https://docs.appuio.ch/managed-openshift/gitops/howto-argocd.html[our documentation].
3 changes: 3 additions & 0 deletions docs/modules/ROOT/partials/nav.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -182,6 +182,9 @@
** xref:oc4:ROOT:how-tos/monitoring/handle_alerts.adoc[]
** xref:oc4:ROOT:how-tos/monitoring/remove_rules.adoc[]

* GitOps
** xref:oc4:ROOT:how-tos/gitops/cluster-scope-argocd.adoc[Configure Cluster Scope ArgoCD Instances]

// Scalability and performance
// Specialized hardware and driver enablement

Expand Down