kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update for use of feature gates

This commit is contained in:
Robert Krawitz 2018-09-17 12:52:14 -04:00
parent 3a19ee6516
commit 3980916f68
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
keps/sig-node/0028-20180906-quotas-for-ephemeral-storage.md
View File

@ -38,6 +38,7 @@ superseded-by:
* [Goals](#goals)
* [Non-Goals](#non-goals)
* [Proposal](#proposal)
* [Control over Use of Quotas](#control-over-use-of-quotas)
* [Operation Flow -- Applying a Quota](#operation-flow----applying-a-quota)
* [Operation Flow -- Retrieving Storage Consumption](#operation-flow----retrieving-storage-consumption)
* [Operation Flow -- Removing a Quota.](#operation-flow----removing-a-quota)
@ -242,6 +243,23 @@ consistent with the desired limit. If we elect to use it as
non-enforcing, we impose a large quota that in practice cannot be
exceeded (2^63-1 bytes for XFS, 2^58-1 bytes for ext4fs).
### Control over Use of Quotas
At present, three feature gates control operation of quotas:
* `LocalStorageCapacityIsolation` must be enabled for any use of
quotas.
* `FSQuotaForLSCIMonitoring` must be enabled in addition. If this is
enabled, quotas are used for monitoring, but not enforcement. At
present, this defaults to False, but the intention is that this will
default to True by initial release.
* `FSQuotaForLSCIEnforcement` must be enabled, in addition to
`FSQuotaForLSCIMonitoring`, to use quotas for enforcement. This
defaults to False and is expected to remain in that state for
initial release.
### Operation Flow -- Applying a Quota
* Caller (emptydir volume manager or container runtime) creates an