> On Apr 9, 2024, at 9:48 PM, Weiwei Yang wrote:
>
> My concern is from another angle, though the plugin mode is not as
> elegant as the standalone mode, it works and serves the purpose of
> bringing yunikorn values without breaking existing things.
Except that the plugin mode does “break
Hi Craig
Thanks for the write-up and it clearly explains the rationale behind this.
I appreciate you listing all these things in detail to help all community
members understand
in depth about the issue. Thank you!
I agree with all the points you listed. My concern is from another angle,
though
Hi all,
thanks Craig for writing this excellent, detailed summary, including
historical context.
As we already talked about it on Slack, I'm definitely +1 for removing the
plugin. My main gripes are:
1. It overcomplicates the codebase. Two branches for plugin vs non-plugin
mode, scheduler cache
---
Preface
===
There have been quite a few informal discussions on this topic, and it's time
that we bring this formally to the yunikorn-dev mailing list for further
discussion...
---
Summary
===
We are actively planning to deprecate the YuniKorn plugin mode for eventual
