You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What kind of request is this (question/bug/enhancement/feature request):
Enhancement
Description
High ephemeral storage usage causes node unavailability, Pod evictions.
It would be good to have an option to set an ephemeral storage limit at the namespace/project level to control the space usage to avoid these situations.
As per below comment, the ephemeral-storage limits were not enabled as it was alpha #13277 (comment)
// The resource name for ResourceEphemeralStorage is alpha and it can change across releases.
ResourceEphemeralStorage ResourceName = "ephemeral-storage"
The text was updated successfully, but these errors were encountered:
ansilh
changed the title
[RFE] Add option to set ephemeral-storage quota in Project
[RFE] Add option to set ephemeral-storage quota in Project/Namespace
Nov 9, 2020
The current mechanism relies on periodically walking each ephemeral volume (emptydir, logdir, or container writable layer) and summing the space consumption.
This method is slow, can be fooled, and has high latency (i. e. a pod could consume a lot of storage prior to the kubelet being aware of its overage and terminating it).
What kind of request is this (question/bug/enhancement/feature request):
Enhancement
Description
High ephemeral storage usage causes node unavailability, Pod evictions.
It would be good to have an option to set an ephemeral storage limit at the namespace/project level to control the space usage to avoid these situations.
As per below comment, the ephemeral-storage limits were not enabled as it was alpha
#13277 (comment)
Based on the upstream k8s code comment, the name of the resource is alpha.
https://github.com/kubernetes/kubernetes/blob/release-1.19/pkg/apis/core/types.go#L4182
As per below PR , the feature itself is moved to beta
kubernetes/kubernetes#60159
gz#13239
The text was updated successfully, but these errors were encountered: