-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
[pending UserNamespace beta]promote LocalStorageCapacityIsolationFSQuotaMonitoring to beta #112626
Conversation
/test pull-kubernetes-node-kubelet-serial-crio-cgroupv1 |
@@ -939,7 +940,7 @@ var defaultKubernetesFeatureGates = map[featuregate.Feature]featuregate.FeatureS | |||
|
|||
LocalStorageCapacityIsolation: {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.27 | |||
|
|||
LocalStorageCapacityIsolationFSQuotaMonitoring: {Default: false, PreRelease: featuregate.Alpha}, | |||
LocalStorageCapacityIsolationFSQuotaMonitoring: {Default: true, PreRelease: featuregate.Beta}, |
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.
is the isue fix in this pr: #112625? Is this PR just WIP than?
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 this should be pending until #112625 is merged to fix the regression.
I still need more verifying for the fix.
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.
Since the fsquota related bug is fixed, I think we can promote it again. I will update the KEP as soon as possible in kubernetes/enhancements#3821
6441bbe
to
9715ba4
Compare
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/assign @rphillips Let's evaluate whether we can really promote it to beta as there seems to be bugs still that needs to be looked at. /hold |
/unhold |
@rphillips @SergeyKanzhelev @derekwaynecarr Do you have any comments on this feature promotion? |
/assign @derekwaynecarr |
Ping again before the code freeze. |
@mrunalp @haircommander do you have the kernel issue link? |
It's not so much an issue as expected behavior, and actually I may have been wrong. Any process in the root user namespace can change the project ID of a path, effectively nullifying the quota for a malicious user. In some of the documentation, users need CAP_SYS_RESOURCE to change the hard limit, and I'm not sure if that also applies to changing the project ID. there seems to have been a discussion on this but it's not clear where this went. I am trying to investigate further. If a user does need CAP_SYS_RESOURCE to change a project ID, then we're good to move forward with this beta IMO. Otherwise, we will need to wait until user namespaces are more prevalent to move forward with this feature |
Okay I confirmed with kernel engineer. It's not actually documented other than in the code, but a process just needs to own the file or have CAP_FOWNER. If it's in a user namespace it can't change the projid, so we would need to require user namespace support. Theoretically we could pursue beta for this in 1.30, since we're pushing for user namespace beta then, but we may want to wait for the feature to be on by default (maybe 1.31?) |
I may update the KEP based on this.
As a risk, we'd better to wait for User Namespace beta before promoting this to beta in my opinion. |
yeah probably
works for me! |
/remove-priority important-soon |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
This reverts commit 32a90f5.
This feature gate was promoted to beta only in v1.25.0 and was reverted in v1.25.1 for a regression issue.
See the history in #107329 and #112076
The KEP can be found in kubernetes/enhancements#2697
Action Items:
it's in a user namespace it can't change the projid
and if not, project ID could be changed. So we want to wait for User Namespace beta before promoting this to beta./kind feature
Xrefs kubernetes/enhancements#1029