-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.17, 4.18
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
customLogoFile settings is present in spec.customization by default, also the name is empty
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-2024-10-22-175936
How reproducible:
Always
Steps to Reproduce:
1. Check default spec.customization settings
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.18.0-0.nightly-2024-10-22-175936 True False 99m Cluster version is 4.18.0-0.nightly-2024-10-22-175936
$ oc get console.operator cluster -o json | jq .spec.customization
{
"addPage": {},
"capabilities": [
{
"name": "LightspeedButton",
"visibility": {
"state": "Enabled"
}
},
{
"name": "GettingStartedBanner",
"visibility": {
"state": "Enabled"
}
}
],
"customLogoFile": {
"name": ""
},
"developerCatalog": {
"types": {
"state": "Enabled"
}
},
"projectAccess": {},
"quickStarts": {}
}
Actual results:
$ oc get console.operator cluster -o json | jq .spec.customization.customLogoFile
{
"name": ""
}
customLogoFile name value is empty
Expected results:
customLogoFile settings seem should not be presented by default
Additional info: