-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Fix default handling of pids-limit #17262
Fix default handling of pids-limit #17262
Conversation
Add test to verify that updates without a pids-limit specified no longer overwrite the previous value. Also fixes erroneous warning generated by remote clients: "Resource limits are not supported and ignored on cgroups V1 rootless systems" Signed-off-by: Jason T. Greene <[email protected]>
/approve |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: n1hility, rhatdan 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 |
/cherry-pick v4.4 |
@baude: new pull request created: #17355 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/test-infra repository. |
I noticed container creation/run commands on podman remote were printing:
"Resource limits are not supported and ignored on cgroups V1 rootless systems"
The underlying cause was a problem with default handling introduced in the enhancement that added pids-limit for container update operations (479052a)
This also meant that updates for other values would unintentionally change the pids-limit back to the default value. This PR adds a test for that condition as well.
Signed-off-by: Jason T. Greene [email protected]
Does this PR introduce a user-facing change?