-
Notifications
You must be signed in to change notification settings - Fork 368
MON-3163: support VPAs #2078
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-3163: support VPAs #2078
Conversation
@rexagod: This pull request references MON-3163 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. |
1 similar comment
@rexagod: This pull request references MON-3163 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. |
Skipping CI for Draft Pull Request. |
@rexagod: This pull request references MON-3163 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. |
4120fa0
to
a619580
Compare
@rexagod: This pull request references MON-3163 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. |
@rexagod: This pull request references MON-3163 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. |
@rexagod: This pull request references MON-3163 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. |
/jira refresh |
@rexagod: This pull request references MON-3163 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. |
/cc |
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.
I've done a first pass, things looks good.
I find the new jsonnet file a little hard to follow, but I need to reacquaint myself a bit with jsonnet before I'll come back with something constructive.
Proposed some jsonnet changes in rexagod#1 |
/retest |
@rexagod: This pull request references MON-3163 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 task to target the "4.15.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 kubernetes/test-infra repository. |
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jan--f, rexagod 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 |
@rexagod feel free to unhold unless this still needs review from a VPA team. |
@jan--f Just to clarify, do you mean the Node team (Joel)? They were the ones with this request initially. Or should I ping the autoscaling team to get a review here? PS. As you know, VPA metrics being introduced here are more of a "re-introduction" since these used to exist within KSM before being deprecated, adhering to the same behavior that they had, so I believe we should be safe to |
You added a hold a while back in #2078 (comment) I just didn't want to preempt anything. Feel free to unhold unless you want anyone else's eyes on this. |
ACK, I've pinged the autoscaling team to take a look. 🤞🏼 |
/test e2e-aws-ovn-single-node We might have to skip this one, since the failures do not indicate any issues with the patch itself. |
The single node test is not required...that won't block the merge. Only the |
LGTM, thanks! |
/unhold Thanks, Joel! Unholding now. |
/retest |
/hold |
Simon and I went over this here: #2078 (comment), PTAL. |
thanks for the explanation, let the kube-state-metrics pod run for a few time, the error only shown once, delete the kube-state-metrics pod, watch for a while, no such errors. |
/label qe-approved |
@rexagod: This pull request references MON-3163 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 openshift-eng/jira-lifecycle-plugin repository. |
/retest |
/hold Just to make sure #2078 (comment) looks good to Jan, in which case, feel free to unhold. |
Thanks for the details. |
@rexagod: 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. |
[ART PR BUILD NOTIFIER] This PR has been included in build cluster-monitoring-operator-container-v4.16.0-202404261114.p0.g77f948e.assembly.stream.el9 for distgit cluster-monitoring-operator. |
Note: This requires the latest KSMv2.10 release to work.
Introduce and leverage KSM's CRS featureset and support VPAs using that.
Details
Logs
Query
Generated
ConfigMap