This helps avoid needing to add an OperatorConfig status field, since OperatorConfig no longer generates any configurations.
Now when KubeletScraping is set, a ClusterNodeMonitoring object is created automatically, reducing duplicated code. Users also have more control over the configuration, since they could change default values.
Later when we remove KubeletScraping, users would already have a ClusterNodeMonitoring so they will not lose their configurations.
This helps avoid needing to add an
OperatorConfigstatus field, sinceOperatorConfigno longer generates any configurations.Now when
KubeletScrapingis set, aClusterNodeMonitoringobject is created automatically, reducing duplicated code. Users also have more control over the configuration, since they could change default values.Later when we remove
KubeletScraping, users would already have aClusterNodeMonitoringso they will not lose their configurations.