Skip to content

Conversation

@nirdothan
Copy link
Member

What this PR does / why we need it:
Remove redundant node optimization requirements which are no longer required, and update some stale information that is no longer relevant.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

Release note:

NONE

@kubevirt-bot kubevirt-bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Sep 25, 2025
@nirdothan
Copy link
Member Author

@kubevirt-bot
Copy link
Contributor

@nirdothan: GitHub didn't allow me to request PR reviews from the following users: sbrivio-rh.

Note that only kubevirt members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @orelmisan @frenzyfriday @sbrivio-rh

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.

@sbrivio-rh
Copy link

It all looks good to me!

Just a note about wmem_max and rmem_max tuning: the current status is that we haven't assessed performance benefits and drawbacks with those in a long time. We have limited evidence that they're not necessary because TCP auto-tuning appears to do the trick nowadays (especially in combination with the vhost-user interface), but we didn't really run a thorough comparison. We have https://bugs.passt.top/show_bug.cgi?id=138 filed for that.

For the moment being, I think it makes sense to drop those from the user guide, and re-introduce them (with whatever value) in the unlikely case we find they still give us a substantial throughput advantage.

Copy link
Member

@orelmisan orelmisan left a comment

Choose a reason for hiding this comment

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

Thank you for the PR @nirdothan!
Just one small comment.

The relevant sidecar image needs to be accessible by the cluster and
specified in the Kubevirt CR when registering the network binding plugin.
### Feature Gate
Copy link
Member

Choose a reason for hiding this comment

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

This section needs to be retained for backward compatibility with KubeVirt versions prior to v1.5, which are still within our support window. Additionally, this change appears unrelated to the optimizations described in the commit message.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done

Copy link
Contributor

Choose a reason for hiding this comment

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

you might want to see conflicts about #926

imo keep the PR focusing only on the optimization req, nothing else

@nirdothan
Copy link
Member Author

Restored FG section fot the benefit of legacy versions <1.15 users.

"computeResourceOverhead": {
"requests": {
"memory": "500Mi",
"memory": "250Mi",
Copy link
Contributor

Choose a reason for hiding this comment

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

regarding memory changes
there is lgtmed PR that already does those
#916

if something is missing, it is better to comment there instead please

Copy link
Member Author

Choose a reason for hiding this comment

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

Won't the merge take care of that?

Copy link
Contributor

Choose a reason for hiding this comment

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

if 916 is merged first then yes, otherwise, it doesnt make sense to include it in this PR
so in both cases it doesnt need to be in this PR, moreover it is not related to PR desc

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't see how this can cause a problem, and 916 should be merged.

### Feature Gate
If not already set, add the `NetworkBindingPlugins` FG.
### Feature Gate - prior to v1.15
For KubeVirt versions prior to 1.15, make sure to enable the `NetworkBindingPlugins` FG.
Copy link
Member

Choose a reason for hiding this comment

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

There is a typo in the version number (twice).
Please consider dropping the prior to v1.15 suffix from the title.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done.

Remove redundant node optimization requirements which are
no longer required, and update some stale information that
is no longer relevant.

Signed-off-by: Nir Dothan <[email protected]>
@nirdothan
Copy link
Member Author

nirdothan commented Sep 29, 2025

Fixed typos.

Copy link
Member

@orelmisan orelmisan left a comment

Choose a reason for hiding this comment

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

Thank you @nirdothan!
/approve

@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: orelmisan

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 29, 2025
Copy link

@frenzyfriday frenzyfriday left a comment

Choose a reason for hiding this comment

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

/lgtm

Thanks!

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Sep 30, 2025
@kubevirt-bot kubevirt-bot merged commit 79896bf into kubevirt:main Sep 30, 2025
6 checks passed
@orelmisan orelmisan mentioned this pull request Sep 30, 2025
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. size/S

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants