Document API/boundary between kubeflow and non Kubeflow platforms

[jlewi]

Fairing defines Cloud Native APIs; e.g. preprocessors, builders, deployer.

Its possible to implement these APIs to support deploying on non-Kubeflow platform; e.g. various SAAS or Cloud provided ML platforms.

There should be a clear boundary between neutral/reusable code and vendor specific code.

That boundary should be a Cloud/Kubernetes Native API. This is in keeping with the principles of Kubeflow that Kubeflow is Kubernetes native.

We should document what this API is so that we can provide clear guidance to vendors looking to add support for their platform.

/cc @karthikv2k @r2d4

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label improvement/enhancement to this issue, with a confidence of 0.95. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[jlewi]

@karthikv2k Is this on track for 0.6? Should we punt to 0.7?

[karthikv2k]

We have no cycles to do this in 0.6 so removed it from 0.6 board.