Should training operator keep clientset in the same repository?

[Jeffwan]

There's discussion with @andreyvelich here #1320 (comment)
@zw0610 also mentioned this when we start all-one-one operator project.

it depends on whether we have upstream, (I do think so. ) Having separate repo is easier for any project to import and that's pretty clean. Otherwise, user have to import entire project which is still acceptable and they need to take care of the dependencies.

While, it might be hard for us to open a new repo for training apis. Probably good for all kubeflow apis?

[zw0610]

I think the main point is to separate apis and clientsets. The generation of clientsets introduces a specific client-go version, which maybe troublesome for developers on client-go version control.

[gaocegege]

I think the main point is to separate apis and clientsets. The generation of clientsets introduces a specific client-go version, which maybe troublesome for developers on client-go version control.

Do you mean we need three repos?

[Jeffwan]

/kind discussion

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.