Skip to content

Commit 592b064

Browse files
DebarghoGhoshDebarghoGhosh
committed
added setting up argo cd instance
made review changes made review changes rectified typo swapped steps made review changes made review changes made review changes made review changes made changes removed extra lines changed modules included made review changes made review changes
1 parent 8b46e72 commit 592b064

File tree

5 files changed

+101
-0
lines changed

5 files changed

+101
-0
lines changed

‎_topic_maps/_topic_map.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1596,6 +1596,8 @@ Topics:
15961596
File: installing-openshift-gitops
15971597
- Name: Uninstalling OpenShift GitOps
15981598
File: uninstalling-openshift-gitops
1599+
- Name: Setting up a new Argo CD instance
1600+
File: setting-up-argocd-instance
15991601
- Name: Configuring an OpenShift cluster by deploying an application with cluster configurations
16001602
File: configuring-an-openshift-cluster-by-deploying-an-application-with-cluster-configurations
16011603
- Name: Deploying a Spring Boot application with Argo CD

‎cicd/gitops/setting-up-argocd-instance.adoc

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
:_content-type: ASSEMBLY
2+
[id="setting-up-argocd-instance"]
3+
= Setting up a new Argo CD instance
4+
include::_attributes/common-attributes.adoc[]
5+
:context: setting-up-argocd-instance
6+
7+
toc::[]
8+
9+
By default, the {gitops-title} installs an instance of Argo CD in the `openshift-gitops` namespace with additional permissions for managing certain cluster-scoped resources. To manage cluster configurations or deploy applications, you can install and deploy a new Argo CD instance. By default, any new instance has permissions to manage resources only in the namespace where it is deployed.
10+
11+
include::modules/gitops-argo-cd-installation.adoc[leveloffset=+1]
12+
13+
include::modules/gitops-enable-replicas-for-argo-cd-server.adoc[leveloffset=+1]
14+
15+
include::modules/gitops-deploy-resources-different-namespaces.adoc[leveloffset=+1]

‎modules/gitops-argo-cd-installation.adoc

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * gitops-argo-cd-installation.adoc
4+
5+
:_content-type: PROCEDURE
6+
[id="gitops-argo-cd-installation_{context}"]
7+
= Installing Argo CD
8+
9+
To manage cluster configurations or deploy applications, you can install and deploy a new Argo CD instance.
10+
11+
.Procedure
12+
. Log in to the {product-title} web console.
13+
14+
. Click *Operators* -> *Installed Operators*.
15+
16+
. Create or select the project where you want to install the Argo CD instance from the *Project* drop-down menu.
17+
18+
. Select *Openshift GitOps Operator* from the installed operators and select the *Argo CD* tab.
19+
20+
. Click *Create* to configure the following parameters:
21+
22+
.. For *Name*, enter `/`.
23+
24+
.. Create an external OS Route to access Argo CD server. Click *Server* -> *Route* and, for *Enable Route*, select *true*.
25+
26+
. To open the Argo CD web UI, click the route that is created in the project where the Argo CD instance is installed.

‎modules/gitops-deploy-resources-different-namespaces.adoc

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * gitops-argo-cd-installation.adoc
4+
5+
:_content-type: PROCEDURE
6+
[id="gitops-deploy-resources-different-namespaces_{context}"]
7+
= Deploying resources to a different namespace
8+
9+
To allow Argo CD to manage resources in other namespaces apart from where it is installed, configure the target namespace with a `argocd.argoproj.io/managed-by` label.
10+
11+
.Procedure
12+
13+
* Configure the namespace:
14+
+
15+
[source,terminal]
16+
----
17+
$ oc label namespace <namespace> && \
18+
argocd.argoproj.io/managed-by=<instance_name> <1>
19+
----
20+
<1> The namespace where Argo CD is installed.
21+

‎modules/gitops-enable-replicas-for-argo-cd-server.adoc

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * gitops-argo-cd-installation.adoc
4+
5+
:_content-type: PROCEDURE
6+
[id="gitops-enable-replicas-for-argo-cd-server_{context}"]
7+
= Enabling replicas for Argo CD server and repo server
8+
9+
Argo CD-server and Argo CD-repo-server workloads are stateless. To better distribute your workloads among pods, you can increase the number of Argo CD-server and Argo CD-repo-server replicas. However, if a horizontal autoscaler is enabled on the Argo CD-server, it overrides the number of replicas you set.
10+
11+
.Procedure
12+
13+
* Set the `replicas` parameters for the `repo` and `server` spec to the number of replicas you want to run:
14+
+
15+
.Example Argo CD custom resource
16+
17+
[source,yaml]
18+
----
19+
apiVersion: argoproj.io/v1alpha1
20+
kind: ArgoCD
21+
metadata:
22+
name: example-argocd
23+
labels:
24+
example: repo
25+
spec:
26+
repo:
27+
replicas: <number_of_replicas>
28+
server:
29+
replicas: <number_of_replicas>
30+
route:
31+
enabled: true
32+
path: /
33+
tls:
34+
insecureEdgeTerminationPolicy: Redirect
35+
termination: passthrough
36+
wildcardPolicy: None
37+
----

0 commit comments

Comments
 (0)