You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/modules/ROOT/pages/references/parameters.adoc
+104-1Lines changed: 104 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,6 +121,12 @@ This allows users to remove links which were configured higher up in the hierarc
121
121
type:: dictionary
122
122
default:: `{}`
123
123
124
+
[NOTE]
125
+
====
126
+
This parameter is deprecated on OpenShift 4.19 and newer.
127
+
Use `custom_logos` and `custom_favicon` instead.
128
+
====
129
+
124
130
Add a custom logo to the console.
125
131
Takes a single key with the filename and the value is the base64 encoded logo.
126
132
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
@@ -131,13 +137,110 @@ The filename needs to have a filename extension which matches the image format.
131
137
For SVG logos the file must *not* be base64 encoded, but inserted directly as a string.
132
138
====
133
139
134
-
By default, OCP won't serve a favicon if a custom logo is configured for the console.
140
+
By default, OpenShift won't serve a favicon if a custom logo is configured for the console.
135
141
This is an intentional design decision as documented in this https://bugzilla.redhat.com/show_bug.cgi?id=1844883#c1[bug report].
136
142
137
143
The component tries to ensure that a favicon is served even if a custom logo is configured.
138
144
However, because the current workaround for the missing favicon requires an additional custom route for the console hostname, it can only be implemented for configurations which use a custom console hostname.
139
145
Otherwise, the component is unable to correctly configure `spec.hostname` for the console.
This parameter only has an effect on OpenShift 4.19 and newer.
155
+
For older versions of OpenShift, use parameter `custom_logo`.
156
+
157
+
OpenShift 4.19 introduces a new console look with a dark and light theme.
158
+
The new custom logo mechanism allows configuring separate logos for each theme.
159
+
The component supports keys `dark` and `light` to specify logos for the dark and light theme respectively.
160
+
The component additionally supports specifying a single logo for all themes in key `'*'`.
161
+
If there's no logo for a theme, the console will show the default logo for that theme.
162
+
163
+
Each 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.
164
+
165
+
The component looks for fields `type` and `data` in each entry of the parameter.
166
+
Field `type` is expected to be a valid file extension in all lower case matching the image data provided in field `data`.
167
+
Field data is the logo image data, in plain text for SVG and base64 encoded for all other formats.
168
+
169
+
The component will render all the logos in a single ConfigMap.
170
+
The component will dynamically add logos to fields `data` (for SVG) and `binaryData` (for other formats) in the ConfigMap.
171
+
172
+
Additionally, the component will configure an entry in `spec.customization.logos` in the `console.operator.openshift.io` custom resource to actually configure the custom logos.
<2> All other formats, such as PNG need to be configured base64 encoded
226
+
227
+
== `custom_favicon`
228
+
229
+
[horizontal]
230
+
type:: dictionary
231
+
default:: `{}`
232
+
233
+
Starting with OpenShift 4.19, users can configure custom favicons for the console.
234
+
This parameter has no effect on OpenShift versions before 4.19.
235
+
236
+
OpenShift 4.19 supports specifying separate favicons for the dark and light themes, but the component currently only supports configuring a single favicon for both themes.
237
+
238
+
The component looks for fields `type` and `data` in the parameter.
239
+
Field `type` is expected to be a valid file extension in all lower case matching the image data provided in field `data`.
240
+
Field data is the favicon data, in plain text for SVG and base64 encoded for all other formats.
241
+
242
+
The component will write the favicon into a ConfigMap and configure an entry in `spec.customization.logos` in the `console.operator.openshift.io` custom resource to enable the custom favicon for the console.
0 commit comments