-
Notifications
You must be signed in to change notification settings - Fork 266
net, passt: Rm optimization requirements #933
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
|
@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: 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. |
|
It all looks good to me! Just a note about 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. |
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.
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 |
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.
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.
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.
Done
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.
you might want to see conflicts about #926
imo keep the PR focusing only on the optimization req, nothing else
0d9be45 to
68f997d
Compare
|
Restored FG section fot the benefit of legacy versions <1.15 users. |
| "computeResourceOverhead": { | ||
| "requests": { | ||
| "memory": "500Mi", | ||
| "memory": "250Mi", |
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.
regarding memory changes
there is lgtmed PR that already does those
#916
if something is missing, it is better to comment there instead 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.
Won't the merge take care of that?
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.
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
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 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. |
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.
There is a typo in the version number (twice).
Please consider dropping the prior to v1.15 suffix from the title.
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.
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]>
68f997d to
7c37e6d
Compare
|
Fixed typos. |
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.
Thank you @nirdothan!
/approve
|
[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 |
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
Thanks!
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: