Add "Standalone Components" section to "Installing Kubeflow" #3726
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is intended as an alternative to the proposal from @andreyvelich in #3724.
The goal of this PR is to reduce confusion, while still meeting the request of @andreyvelich to tell users that some components may be installed separately.
The main change is the addition of a "Standalone Components" section on the "Installing Kubeflow".
This "Standalone Components" section has a table which lists if each component of Kubeflow is able to be deployed "standalone", that is, without the rest of the platform.
/assign @kubeflow/wg-notebooks-leads @kubeflow/wg-pipeline-leads @kubeflow/wg-training-leads @kubeflow/wg-data-leads @kubeflow/release-team @kubeflow/kubeflow-steering-committee @kubeflow/wg-deployment-leads
Screenshot
Here is a screenshot of the updated "Installing Kubeflow" page: