MON-3183: Expose and propagate TopologySpreadConstraints for UWM prometheus #2038
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@marioferh: This pull request references MON-3183 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
openshift-ci
bot
added
the
approved
Signed-off-by: Mario Fernandez <mariofer@redhat.com>
marioferh
force-pushed
the
topology_spread_constrains_UWM_prometheus
branch
from
828cb0f
to
7be0b56
Compare
|
@marioferh: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: marioferh, raptorsun The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Give users a TopologySpreadConstraints field in the PrometheusRestrictedConfig field and propagate this to the pod that is created.