VPA Scheduled on Master Nodes

[scottd018]

Is there a reason that the VPA operator is scheduled on the master nodes as part of the operator installation process? See https://github.com/openshift/vertical-pod-autoscaler-operator/blob/master/install/deploy/03_deployment.yaml#L56

From the upstream (https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler/deploy) it looks like this is not a hard requirement for the project.

The reason I ask, is it creates a problem with our managed cloud services (e.g. ROSA), specifically with Hosted Control Plane which do not expose any master nodes within the cluster, which creates a poor experience for those users.

Happy to PR if we can remove this requirement, otherwise was curious to discuss.

FWIW, we were able to work around this by editing the Subscription resource following a failed deployment, but that is not ideal from a UX perspective IMO:

spec:
  channel: stable
  config:
    nodeSelector:
      node-role.kubernetes.io/worker: ""

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale