openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-07 00:48:01 +01:00
Code Issues Releases Activity

Applying style edits to the Web console section

Browse Source
This commit is contained in:
Ashley Hardin
2020-11-16 14:03:20 -05:00
parent af6c77c021
commit f358daade8
2 changed files with 21 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
modules/adding-a-custom-logo.adoc
View File

@@ -5,20 +5,16 @@
[id="adding-a-custom-logo_{context}"]
= Adding a custom logo and product name
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.
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.
.Prerequisites
* You must have administrator privileges.
* 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`.
* 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`.
.Procedure
. Import your logo file into a ConfigMap in the `openshift-config` namespace:
. Import your logo file into a config map in the `openshift-config` namespace:
+
[source,terminal]
----
@@ -46,13 +42,9 @@ spec:
customProductName: My Console
----
+
Once the Operator configuration is updated, it will sync the custom logo
ConfigMap into the console namespace, mount it to the console pod, and redeploy.
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.
. Check for success. If there are any issues, the console cluster operator will
report `Degraded`, and the console Operator configuration will also report
`CustomLogoDegraded`, but with reasons like `KeyOrFilenameInvalid` or
`NoImageProvided`.
. 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`.
+
To check the `clusteroperator`, run:
+

16
modules/customizing-the-login-page.adoc
View File

@@ -22,7 +22,15 @@ pages during the authentication process.
[source,terminal]
----
$ oc adm create-login-template > login.html
----
+
[source,terminal]
----
$ oc adm create-provider-selection-template > providers.html
----
+
[source,terminal]
----
$ oc adm create-error-template > errors.html
----
@@ -31,7 +39,15 @@ $ oc adm create-error-template > errors.html
[source,terminal]
----
$ oc create secret generic login-template --from-file=login.html -n openshift-config
----
+
[source,terminal]
----
$ oc create secret generic providers-template --from-file=providers.html -n openshift-config
----
+
[source,terminal]
----
$ oc create secret generic error-template --from-file=errors.html -n openshift-config
----