The message from the Apache YuniKorn Github is a bit confusing when we put YARN, and “general scheduler” together.
For most of the companies we spoke to, initially, they’re confused with: Is it a K8s scheduler, or it is a YARN RM but hook up with K8s. I think we need to do massive work to make the marketing message correct.
To me, the #1 use case YuniKorn trying to solve now is to be the best scheduler in K8s to solve batch workload problems.
It is nicely designed to allow yunikorn-core to hook up with other RMs, but that is the next step.
We can also include other items like highlights of K8s integration, perf test, and community sync ups to the same README.