-
Notifications
You must be signed in to change notification settings - Fork 38.8k
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
eviction_manager _test.go should have unit tests that cover localStorageCapacityIsolation #120062
Comments
/cc @jingxu97 |
I can help with this. can you assign me after jingxu replies to you?(for more context here) @kannon92 |
that would be great @charles-chenzz ! |
you're welcome. do you have any context here that why didn't cover localStorageCapacityIsolation? |
I don't recall a specific reason. The feature was implemented a while back. |
/assign |
Hey @charles-chenzz Are you still working. If not can I take this up? |
@Sajiyah-Salat hi, yes I'm still working on it |
@charles-chenzz hii I am new to k8s , so i wanna know can I use windows os for it? if yes would you show me how to get nodes... |
hi, the answer is yes you can use windows and I think if you need support you better open another issue and @ me there, as this issue is not for discuss how to run k8s on windows @shindodkar |
/remove-kind bug |
I see https://github.com/kubernetes/kubernetes/pull/119570/files and I am wondering if we have duplicated efforts here. @claassen did you end up testing this path in our above PR? |
Hey, @kannon92 is someone working on this issue ? or let me know if someone need help |
@kannon92 Happy to help with this. Do you still need help |
@kannon92 hey, is this currently still unassigned |
@charles-chenzz has a #120185 ready for approval. /remove-good-first-issue |
As I was reading the test code, I noticed that we are missing a pretty large chunk of logic around localStorageCapacityIsolation.
This feature was GA in 1.25 so it would be ideal to have unit test coverage around this code.
This code monitors whether or not there is a violation in temporary storage and if there is it would evict the pod.
One should be able to intiailize the manager with
localStorageCapacityIsolation
of true and then write some test cases to verify this behavior./help
/sig node
/good-first-issue
/kind bug
The text was updated successfully, but these errors were encountered: