Kube version specific Scheduler image

[mhmxs]

No description provided.

[croomes]

Can you still set your own scheduler image? This will be needed for air-gapped installs.

We'd previously discussed trying to detect the image currently being used by the cluster but we couldn't find a foolproof way. I can see component=kube-scheduler is being set on my Kind cluster - if this is standard across distributions maybe it could be used, with appropriate fallback?

[mhmxs]

@croomes There are 2 options to set the scheduler image. One is related images stuff in kube manifest level and cluster config also has a field. If non of them had found, operator uses the Kube version specific one.
I don't see the relation between in cluster scheduler version and our scheduler version. Scheduler is released with Kubernetes, so if we have the server version we are able to use the right version of scheduler.

Anyway I don't want/suggest to change something like this in the last minute before release. WDT?

[croomes]

As long as the user can still override with an internal registry in the StorageOSCluster CR then it's fine.