Skip to content

Commit f358daa

Browse files
committed
Applying style edits to the Web console section
1 parent af6c77c commit f358daa

File tree

2 files changed

+21
-13
lines changed

2 files changed

+21
-13
lines changed

modules/adding-a-custom-logo.adoc

Lines changed: 5 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -5,20 +5,16 @@
55
[id="adding-a-custom-logo_{context}"]
66
= Adding a custom logo and product name
77

8-
You can create custom branding by adding a custom logo or custom product name.
9-
You can set both or one without the other, as these settings are independent of
10-
each other.
8+
You can create custom branding by adding a custom logo or custom product name. You can set both or one without the other, as these settings are independent of each other.
119

1210
.Prerequisites
1311

1412
* You must have administrator privileges.
15-
* Create a file of the logo that you want to use. The logo can be a file in any
16-
common image format, including GIF, JPG, PNG, or SVG, and is constrained to a
17-
`max-height` of `60px`.
13+
* Create a file of the logo that you want to use. The logo can be a file in any common image format, including GIF, JPG, PNG, or SVG, and is constrained to a `max-height` of `60px`.
1814

1915
.Procedure
2016

21-
. Import your logo file into a ConfigMap in the `openshift-config` namespace:
17+
. Import your logo file into a config map in the `openshift-config` namespace:
2218
+
2319
[source,terminal]
2420
----
@@ -46,13 +42,9 @@ spec:
4642
customProductName: My Console
4743
----
4844
+
49-
Once the Operator configuration is updated, it will sync the custom logo
50-
ConfigMap into the console namespace, mount it to the console pod, and redeploy.
45+
Once the Operator configuration is updated, it will sync the custom logo config map into the console namespace, mount it to the console pod, and redeploy.
5146

52-
. Check for success. If there are any issues, the console cluster operator will
53-
report `Degraded`, and the console Operator configuration will also report
54-
`CustomLogoDegraded`, but with reasons like `KeyOrFilenameInvalid` or
55-
`NoImageProvided`.
47+
. Check for success. If there are any issues, the console cluster Operator will report a `Degraded` status, and the console Operator configuration will also report a `CustomLogoDegraded` status, but with reasons like `KeyOrFilenameInvalid` or `NoImageProvided`.
5648
+
5749
To check the `clusteroperator`, run:
5850
+

modules/customizing-the-login-page.adoc

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,15 @@ pages during the authentication process.
2222
[source,terminal]
2323
----
2424
$ oc adm create-login-template > login.html
25+
----
26+
+
27+
[source,terminal]
28+
----
2529
$ oc adm create-provider-selection-template > providers.html
30+
----
31+
+
32+
[source,terminal]
33+
----
2634
$ oc adm create-error-template > errors.html
2735
----
2836

@@ -31,7 +39,15 @@ $ oc adm create-error-template > errors.html
3139
[source,terminal]
3240
----
3341
$ oc create secret generic login-template --from-file=login.html -n openshift-config
42+
----
43+
+
44+
[source,terminal]
45+
----
3446
$ oc create secret generic providers-template --from-file=providers.html -n openshift-config
47+
----
48+
+
49+
[source,terminal]
50+
----
3551
$ oc create secret generic error-template --from-file=errors.html -n openshift-config
3652
----
3753

0 commit comments

Comments
 (0)