Skip to content

Commit fbb29d0

Browse files
committed
Clean up formatting and missing image
1 parent ff047a8 commit fbb29d0

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

content/modules/ROOT/pages/01-getting-started.adoc

+4-6
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,6 @@
22
include::_attributes.adoc[]
33

44
[#cluster-login]
5-
== OpenShift cluster login
6-
75
== OpenShift Cluster Login
86

97
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>&lt
8684
====
8785
8886
[#argocd-login]
89-
= OpenShift GitOps Login
87+
== OpenShift GitOps Login
9088
9189
While Argo CD generates a default `admin` user and a random password when first
9290
deployed you can also configure Argo CD to use the OpenShift authentication.
@@ -113,14 +111,14 @@ Web UI.
113111
image::argocd-login2.png[ArgoCDLogin2, 600]
114112
115113
[#gitops-architecture]
116-
= OpenShift GitOps Architecture
114+
== OpenShift GitOps Architecture
117115
118116
In this section we will do a brief overview of the OpenShift GitOps architecture which is depicted in the diagram below.
119117
120-
image::gitops/argocd-architecture.png[]
118+
image::argocd-architecture.png[]
121119
122120
[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
124122
dependencies or interactions.
125123
126124
The OpenShift GitOps operator is used to deploy, manage and upgrade an installation of Argo CD which runs in a

0 commit comments

Comments
 (0)