-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
Add Policy None for Topology Manager #79343
Add Policy None for Topology Manager #79343
Conversation
Hi @nolancon. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
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.
/ok-to-test
/priority important-soon
} | ||
} | ||
|
||
func TestCanAdmitPodResult2(t *testing.T) { |
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.
Why there is a 2 in the function name?
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.
Strict policy test and preferred policy test have similar functions named ''TestCanAdmitPodResult" and "TestCanAdmitPodResult1" respectively, so just following that naming convention.
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 think renaming it to TestPolicyNoneCanAdmitPodResult is better, and the other tests should be renamed respectively.
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.
Sure, I will update all three.
/kind node |
Update naming of test functions.
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.
Please squash the commits into one, others LGTM
/retest |
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
Modulo, I think I may be missing where we actually make it the default? Or is that going to come later?
Yes, #73580 will be updated to make None the default policy. |
/assign @ConnorDoyle |
@derekwaynecarr @ConnorDoyle could you take a look at this when you get a chance? |
} | ||
|
||
func (p *nonePolicy) Name() string { | ||
return string(PolicyNone) |
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 can remove the string as PolicyNone already a string
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 approved to move this along, but @nolancon if you could clean this up in a follow on. Thanks!
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.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nolancon, sjenning 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 |
/kind feature |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adds 'None' policy for Topology Manager in addition to existing 'Preferred' and 'Strict' policies. 'None' policy will be enabled by default and will do nothing, ensuring current behavior is preserved even if topology manager feature gate is enabled.
As discussed here #74411 (comment)
Does this PR introduce a user-facing change?: