Description of problem:
NodeSelector is not visible on the OLM auto generated form for HCO CR,
see the attached screenshot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. check the form to create a new CR for HCO on OCP 4.6
NodeSelector is not visible
NodeSelector is visible
spec.version is also visible why it should be hidden
Created attachment 1719322 [details]
OLM auto generated form
Simone, despite that the field is not visible in the UI; Can the field be set in the yaml, and will it be recognized?
Yes, it works as expected when the user directly patches the CR but it it's not rendered as expected in the UI nor explained by `oc explain`.
I tend to think we a kubebuilder annotation somewhere.
Let's try to get in fixed in 2.5.0 or 2.5.z at worst.
With https://github.com/kubevirt/hyperconverged-cluster-operator/pull/864 we can get something nicer on the UI because:
- it's using a nicer widget for affinity
- infra and workloads are one after the other
- spec.version is not visible
(see the new screenshots)
Unfortunately NodeSelector is still not visible.
Created attachment 1719766 [details]
OLM form with PR #864
This is a UI issue only
We dont have any custom UI code in the OLM screens, moving to the core
Looked into this. We currently don't support generation of form fields for object schema's with only "additionalProperties" defined. This was an intentional exclusion when scoping the original form generation story. Adding support for this would not be trivial and would require some design consideration.
Closing as this is working as expected. This needs to be handled as an RFE as it will require adding a new feature.