Skip to content

Conversation

@kamarabbas99
Copy link
Contributor

@kamarabbas99 kamarabbas99 commented Nov 13, 2025

What type of PR is this?

/kind feature
/kind api-change

What this PR does / why we need it:

The CPU startup boost chnges were done on experimental branch, moving this to master.

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Users can configure a startupBoost policy in the VPA spec. 

Which issue(s) this PR fixes:

#7862

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]: (https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler/enhancements/7862-cpu-startup-boost#aep-7862-cpu-startup-boost)

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-area area/vertical-pod-autoscaler and removed do-not-merge/needs-area labels Nov 13, 2025
@k8s-ci-robot k8s-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Nov 13, 2025
@kamarabbas99
Copy link
Contributor Author

/cc adrianmoisey omerap12

@k8s-triage-robot
Copy link

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.

Copy link
Member

@omerap12 omerap12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! we already approved this in previous PRs 🥳
/lgtm
/label tide/merge-method-squash

@k8s-ci-robot k8s-ci-robot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Nov 13, 2025
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 13, 2025
@omerap12
Copy link
Member

oh good catch
/lgtm cancel

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 14, 2025
@adrianmoisey
Copy link
Member

adrianmoisey commented Nov 14, 2025

/cc @soltysh
Do you mind doing API review on this?
It was previously reviewed over in #8417, when it was merged into a feature branch.
But now that we're merging it into master, I assume it needs re-review?

@k8s-ci-robot k8s-ci-robot requested a review from soltysh November 14, 2025 06:56
Update VPA version for startupboost feature
@adrianmoisey
Copy link
Member

I'm good with this, thanks for doing it!
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 16, 2025
@omerap12
Copy link
Member

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kamarabbas99, omerap12
Once this PR has been reviewed and has the lgtm label, please assign liggitt for approval. For more information see the Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@soltysh
Copy link
Contributor

soltysh commented Nov 19, 2025

/label api-review

@k8s-ci-robot k8s-ci-robot added the api-review Categorizes an issue or PR as actively needing an API review. label Nov 19, 2025
@soltysh soltysh moved this to Backlog in API Reviews Nov 19, 2025
Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left there a few API related questions, but I didn't get too deep into the logic itself, other than just the validation bits.

// +required
Type StartupBoostType `json:"type" protobuf:"bytes,1,opt,name=type"`
// factor specifies the factor to apply to the resource request.
// This field is to be used only when Type is "Factor".
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// This field is to be used only when Type is "Factor".
// This field is required when Type is "Factor".


// quantity specifies the absolute resource quantity to be used as the
// resource request and limit during the boost phase.
// This field is to be used only when Type is "Quantity".
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// This field is to be used only when Type is "Quantity".
// This field is required when Type is "Quantity".

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sent #8828

maxAllowedCpu: resource.QuantityValue{},
featureGateEnabled: true,
expectError: fmt.Errorf("boost factor must be >= 1"),
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the only error case you're testing, I'd add additional ones for type and factor|quantity specified, and probably also one for invalid type, even though that should be caught at the api server validation, but it doesn't hurt to have a test case covering that.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The other thing, the WithCPUStartupBoost method only modifies the VPA.spec, but doesn't change the container level StartupBoost, it would be good to also cover that case in test, to ensure the latter takes priority.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the relationship between the two, I missed that in the AEP-7862 and the code seems to be working on one or the other, depending on the location?

Copy link
Contributor Author

@kamarabbas99 kamarabbas99 Nov 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added some more error cases in #8828. should it error out when both quantity and Factor are set ? Currently it doesnt.

contianer level startup boost has higher priority, added some test cases to cover that.

kamarabbas99 added a commit to kamarabbas99/autoscaler that referenced this pull request Nov 19, 2025
kamarabbas99 added a commit to kamarabbas99/autoscaler that referenced this pull request Nov 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api-review Categorizes an issue or PR as actively needing an API review. area/vertical-pod-autoscaler cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

8 participants