Hi folks,
Sorry for the last-minute agenda item – I thought it would be a good chance to introduce the KEP since there were no other high-priority topics scheduled for today. I also got the accompanying PoC implementation in working shape earlier this day so I was already thinking hard about the problem. :-)
Anyway, for anyone interested in a QoS-based approach for mitigating the AVX side effect issue, the KEP is here: https://github.com/kubernetes/community/pull/2739 . I think I’ll do also a “do not merge” PR of the PoC code so that the KEP and the code will stay linked together. Let’s talk about the proposal in the 24. October meeting.
Ismo
--
You received this message because you are subscribed to the Google Groups "kubernetes-wg-resource-management" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
kubernetes-wg-resource...@googlegroups.com.
To post to this group, send email to
kubernetes-wg-re...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/kubernetes-wg-resource-management/CAHROWxQMUwEM6Q2qeYf2s1SE5iAdTf%2BaM3tJeWuM3QYCj2d%3DOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.