We need our platform components to set the system-cluster-critical priorityClassName on their workloads. More detail here:
For marketplace this means updating the deployment that generates this pod:
the lastest accepted clusterversion is:4.0.0-0.nightly-2019-03-06-074438
the marketplace's commit is "aabac93da42773f29c4230bd8b7906facc6c42f9" (doesn't include this pr)
will test after this pr is included
cv : 4.0.0-0.alpha-2019-03-13-010143
marketplace image commit:7c6f0bf4b9d0656735e5b39d7fad5f5d411d1bce
The deployment and pod has the PriorityClassName: system-cluster-critical
#oc get deployment marketplace-operator -o yaml | grep critical
# oc describe pod marketplace-operator-745d89bbf4-xkxfh | grep critical
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.