-
Notifications
You must be signed in to change notification settings - Fork 4.3k
feat: CPU startup boost in master #9141
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?
feat: CPU startup boost in master #9141
Conversation
Fix VPA startup boost validation error messages
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: kamarabbas99 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
a687d83 to
419eedc
Compare
|
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
|
/label api-review |
soltysh
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.
I left a few comments for logic. From API shadow perspective this lgtm, I'll try to get API approval on it timely :)
vertical-pod-autoscaler/pkg/apis/autoscaling.k8s.io/v1/types.go
Outdated
Show resolved
Hide resolved
245ad93 to
d8edd78
Compare
| // durationSeconds indicates for how long to keep the pod boosted after it goes to Ready. | ||
| // Defaults to 0. | ||
| // +optional | ||
| DurationSeconds *int32 `json:"durationSeconds,omitempty" protobuf:"varint,4,opt,name=durationSeconds"` |
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.
Can you also update the AEP to reflect this?
(In another PR I guess)
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 updated in the same commit, should I make a new PR just for AEP?
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.
Yes please.
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.
vertical-pod-autoscaler/charts/vertical-pod-autoscaler/crds/vpa-v1-crd-gen.yaml
Show resolved
Hide resolved
vertical-pod-autoscaler/charts/vertical-pod-autoscaler/crds/vpa-v1-crd-gen.yaml
Show resolved
Hide resolved
d8edd78 to
ebdf6fd
Compare
vertical-pod-autoscaler/pkg/apis/autoscaling.k8s.io/v1/types.go
Outdated
Show resolved
Hide resolved
vertical-pod-autoscaler/pkg/apis/autoscaling.k8s.io/v1/types.go
Outdated
Show resolved
Hide resolved
ebdf6fd to
8ed7130
Compare
|
lgtm, anything else from your earlier comments @soltysh ? |
|
PR needs rebase. DetailsInstructions 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. |
soltysh
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.
One comment regarding the naming of a method, to ensure we're not confusing anyone and they you're good to go
| } | ||
|
|
||
| // PodHasCPUBoostInProgress returns true if the pod has the CPU boost annotation. | ||
| func PodHasCPUBoostInProgress(pod *core.Pod) bool { |
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 can't un-resolve the old comment, so leaving a new one. I see that you are indeed using this in 2 more places outside this file. But for the sake of readability let's rename this to match its behavior, iow. PodHasCPUBoostInProgressAnnotation will match better reflect what the method does.
What type of PR is this?
/kind feature
/kind api-change
What this PR does / why we need it:
The CPU startup boost changes were done on experimental branch, moving this to master.
Special notes for your reviewer:
Since #8813 didnt get submitted on time, it was hard to maintain it so as @adrianmoisey suggested I created new PR from local branch directly into master. All of the commits in this PR except the last one have already been reviewed. Reviewed PRs - #8417, #8458, #8618, #8619, #8672, #8789, #8797, #8854, #8863
Does this PR introduce a user-facing change?
Which issue(s) this PR fixes:
#7862
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: