Description of problem:
When viewing the instance of ClusterLogging, the value of Node Selector for all the Logging component like `Kibana Node Selector`, `ElasticSearch Node Selector` etc. is shown `Unsupported`, it should be rather `None` if no NodeSelector is configured of the NodeSelector which is configured.
Version-Release number of selected component (if applicable):
Created attachment 1714463 [details]
Added a screenshot for the same.
Moving to low as setting nodeselectors is possible on all logging components
@Jeff: It's not about the possibility to set a node selector, but about the incorrect display when one is configured!
This is fixed in 4.6, as we moved to properly generated CRDs addressed by . I will close this issue as not a bug.
Created attachment 1715101 [details]
NodeSelectors in 4.6
And to catch the question upfront, we cannot backport the PR to 4.5.z