Skip to content
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

[RFE] Add option to set ephemeral-storage quota in Project/Namespace #29979

Open
ansilh opened this issue Nov 9, 2020 · 2 comments
Open

[RFE] Add option to set ephemeral-storage quota in Project/Namespace #29979

ansilh opened this issue Nov 9, 2020 · 2 comments
Labels

Comments

@ansilh
Copy link

ansilh commented Nov 9, 2020

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

	// The resource name for ResourceEphemeralStorage is alpha and it can change across releases.
	ResourceEphemeralStorage ResourceName = "ephemeral-storage"

As per below PR , the feature itself is moved to beta
kubernetes/kubernetes#60159

gz#13239

@ansilh 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
@ansilh
Copy link
Author

ansilh commented Jul 8, 2021

As per https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1029-ephemeral-storage-quotas

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).

kubernetes/enhancements#1029

@vincebrannon
Copy link

SURE-5144

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants