-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restructured Getting Started Section #888
Restructured Getting Started Section #888
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @dansanche. Thanks for your PR. I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fixes #889 /cc @mameshini What we talked about! |
/assign @mameshini |
/ok-to-test |
Note that I removed the requirements.md and getting-started.md file, and tried to move the important information to the _index.md files instead. Let me know if that works |
/unassign @mameshini @alecglassford Please would you review this PR when it's ready? |
@sarahmaddox: GitHub didn't allow me to assign the following users: alecglassford. Note that only kubeflow members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This should be ready to review now, thanks! |
@dansanche It looks like someone has submitted a change to the file since you forked your branch. To fix, you need to merge in the changes and resolve any conflicts. |
|
||
* [Kubernetes](https://kubernetes.io/docs/tutorials/kubernetes-basics/) | ||
* [TensorFlow](https://www.tensorflow.org/get_started/) | ||
* [ksonnet](https://ksonnet.io/docs/tutorial) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is ksonnet
still a requirement?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not, but I wanted to focus this PR on moving the existing docs around instead of making sure all the content in them is up to date. I believe there are some others working on removing ksonnet from the docs, and I don't want to duplicate their efforts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The removal of ksonnet from this page has already happened:
https://www.kubeflow.org/docs/started/requirements/
The above page is the source of the content that this PR moves to a different page. This is one of the reasons for the merge conflict that GitHub is reporting. Please would you do a careful sync and merge. :)
* An existing Kubernetes cluster using Kubernetes version | ||
{{% kubernetes-min-version %}} or later: | ||
|
||
* A minimum of 0.6 CPU in cluster (Reserved for 3 replicated ambassador pods and according to your need add additional CPUs) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do these general requirements hold for most use cases?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as previous comment. I'm not sure, but I wanted to focus on restructuring existing content rather than verifying its accuracy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally LGTM!
Two nits:
-
You've named the new directories
Cloud
,Local
, andOn-Prem
- why are these capitalized? It seems to be O.K. (they get rendered in lowercase in URLs), but I think giving them lowercase names would fit convention better. Unless there's a reason not to, can you change this? -
Is the distinction between "local hardware" and "on-prem" clear to our audience? I understand that "local hardware" means, like, literally my laptop/development machine vs. "on-prem" means some sort of server/production-ready machine that I own—but at face value the terms sound kind of similar (?). I don't think you necessarily have to change them (and I don't have a good solution), but something to think about.
I think we can try to clarify the differences better in the _index.md files |
/assign |
Hallo @dansanche The second change (putting the info into the _index.md file) breaks the pattern that Docsy provides. For the sake of a consistent experience and ease of maintenance, let's keep the _index.md page as a generated list of links. The first page in the section (https://www.kubeflow.org/docs/started/getting-started/) then gives the primary getting-started instructions. The first change (moving the content from the requirements page to the getting-started page) is a good one. I think we already have an issue for that move - you'll be able to mark that issue as fixed with this PR if you take that change on. (First check that no-one else is doing it already.) Update: Here's the issue, and someone is already working on it: #845 |
/assign @alecglassford |
@sarahmaddox: GitHub didn't allow me to assign the following users: alecglassford. Note that only kubeflow members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I'm curious whether platform, as used in kfctl, is a better use? I find "local" and "on-prem" problematic - maybe "virtual" is better? The reason is that some of these solutions could work up in a public cloud, which wouldn't classify as local or on-prem. |
description = "Get started with Kubeflow on local hardware" | ||
weight = 1 | ||
+++ | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should these be characterized as Local Virtual Machines?
minimal operating system and Kubernetes already installed. | ||
* This option may be useful if you are just starting to learn and already | ||
have one of the virtualization applications installed. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
microk8s will work on any linux system, local or in the cloud. Addtionally, with the advent of WSL2 on Windows, it'll work on Windows too. In the context of local, this will work without a virtual machine. I can make this edit afterwards or as part of this submission. Preference?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After discussing this with Sarah, I'm closing this PR for now. Please give your input on how best to restructure the Getting Started guide here: #889
Closing this and moving related discussion to the issue page |
I was always a bit confused by the getting started section. This PR attempts to restructure it to group together different cloud and local deployment options, and removes some redundant files
old:
new:
This change is