-
Notifications
You must be signed in to change notification settings - Fork 1k
Bump custom-metrics-apiserver version to v1.32.0 #6344
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
Conversation
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #6344 +/- ##
=======================================
Coverage 49.34% 49.34%
=======================================
Files 678 678
Lines 55050 55050
=======================================
Hits 27167 27167
Misses 26115 26115
Partials 1768 1768
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
/retest |
|
Need a rebase for the conflicts~ |
Signed-off-by: wei-chenglai <[email protected]>
79c8cd0 to
d14e17c
Compare
|
Rebased. Thanks for the review! |
RainbowMango
left a comment
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.
/lgtm
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: RainbowMango The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Bump custom-metrics-apiserver with an official release with Kubernetes dependencies v0.32.0 to include k8s dependencies 0.32.
Which issue(s) this PR fixes:
Part of #6310
Special notes for your reviewer:
Does this PR introduce a user-facing change?: