-
Notifications
You must be signed in to change notification settings - Fork 567
MON-4029: Add KubeStateMetrics api #2461
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
base: master
Are you sure you want to change the base?
Conversation
Hello @marioferh! Some important instructions when contributing to openshift/api: |
/retest-required |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actual API for KSM changes seem straightforward and look fine to me.
I noticed there are no integration tests in place. Can we add some simple ones to make sure things like .spec.kubeStateMetricsConfig: {}
isn't valid and help us catch any potential regressions from changes in the future?
5075163
to
e16b37e
Compare
done |
Signed-off-by: Mario Fernandez <[email protected]>
e16b37e
to
74d9f80
Compare
/assign |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few more minor comments, but other than those this LGTM
Signed-off-by: Mario Fernandez <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@marioferh: The following tests failed, say
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-sigs/prow repository. I understand the commands that are listed here. |
// Minimum number of properties: 1. | ||
// Maximum number of properties: 10. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Common OpenShift terminology please.
// When omitted, this means the user has no opinion and the platform is left | ||
// to choose reasonable defaults. These defaults are subject to change over time. | ||
// Defaults are empty/unset. | ||
// When specified, resources must contain at least 1 entry and must not contain more than 10 entries. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// When specified, resources must contain at least 1 entry and must not contain more than 10 entries. | |
// When specified, tolerations must contain at least 1 entry and must not contain more than 10 entries. |
// When omitted, this means no opinion and the platform is left to choose a default, which is subject to change over time. | ||
// This field maps directly to the `topologySpreadConstraints` field in the Pod spec. | ||
// Default is empty list. | ||
// When specified, resources must contain at least 1 entry and must not contain more than 10 entries. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// When specified, resources must contain at least 1 entry and must not contain more than 10 entries. | |
// When specified, topologySpreadConstraints must contain at least 1 entry and must not contain more than 10 entries. |
@marioferh: This pull request references MON-4029 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.21.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
after: #2322