Alexander Zhipa

The fix to simply merge/overwrite existing schedulers is trivial (publishing PR). The only question is whether we want to support the same `_0`/`_1` behavior as for components [here](https://pytorch.org/torchx/main/advanced.html#registering-custom-components)

Do you have any objectsion, @kiukchung , @d4l3k, @tonykao8080, @andywag ?

Just want to check if there are any concerns - otherwise I can contribute @kiukchung , @d4l3k, @tonykao8080, @andywag

Thanks @kiukchung and @d4l3k! Let me process this. I don't want us to add runopts for each and every option k8s has though, I think a generic solution should be...

Same here, do you have any objection, @kiukchung , @d4l3k, @tonykao8080, @andywag ?

Just want to check if there are any concerns - otherwise I can contribute @kiukchung , @d4l3k, @tonykao8080, @andywag

> Thanks for the pull request! Could you please rebase it on the current master branch, so that workflows run correctly? Also I noticed that you have provided an implementation...

> Indenting here is okay, because it uses Material's [content tabs](https://squidfunk.github.io/mkdocs-material/reference/content-tabs/#usage) feature. Exactly, without this change there are no C++/Python tabs to switch from. This follows the same format as...

+1 to what @adamant-pwn said. Also, I've addressed your comment, please let me know if there's more to edit.

The base branch changed, will cut another PR.