New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MON-3177: Expose and propagate TopologySpreadConstraints for kube state metrics #2026
MON-3177: Expose and propagate TopologySpreadConstraints for kube state metrics #2026
Conversation
@marioferh: This pull request references MON-3177 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. |
/test e2e-aws-ovn-single-node |
Signed-off-by: Mario Fernandez <mariofer@redhat.com>
d731adf
to
0a7fc58
Compare
/retest-required |
2 similar comments
/retest-required |
/retest-required |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jan--f, marioferh 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 |
/retest-required |
/retest-required |
@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. |
Give users a TopologySpreadConstraints field in the kubeStateMetrcisConfig field and propagate this to the pod that is created.