File tree 1 file changed +4
-6
lines changed
content/modules/ROOT/pages
1 file changed +4
-6
lines changed Original file line number Diff line number Diff line change 2
2
include::_attributes.adoc[]
3
3
4
4
[#cluster-login]
5
- == OpenShift cluster login
6
-
7
5
== OpenShift Cluster Login
8
6
9
7
The first thing to do is log in to your OpenShift cluster with the following
@@ -86,7 +84,7 @@ use the keyboard to paste content with the shortcut <ctrl><shift><
86
84
====
87
85
88
86
[#argocd-login]
89
- = OpenShift GitOps Login
87
+ == OpenShift GitOps Login
90
88
91
89
While Argo CD generates a default `admin` user and a random password when first
92
90
deployed you can also configure Argo CD to use the OpenShift authentication.
@@ -113,14 +111,14 @@ Web UI.
113
111
image::argocd-login2.png[ArgoCDLogin2, 600]
114
112
115
113
[#gitops-architecture]
116
- = OpenShift GitOps Architecture
114
+ == OpenShift GitOps Architecture
117
115
118
116
In this section we will do a brief overview of the OpenShift GitOps architecture which is depicted in the diagram below.
119
117
120
- image::gitops/ argocd-architecture.png[]
118
+ image::argocd-architecture.png[]
121
119
122
120
[NOTE]
123
- In the diagram above, everything contained within the dotted is running in OpenShift whereas outside the line are external
121
+ In the diagram above, everything contained within the dotted line is running in OpenShift whereas outside the line are external
124
122
dependencies or interactions.
125
123
126
124
The OpenShift GitOps operator is used to deploy, manage and upgrade an installation of Argo CD which runs in a
You can’t perform that action at this time.
0 commit comments