-
Notifications
You must be signed in to change notification settings - Fork 781
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
Test and fix the guide to Microk8s/Multipass for Kubeflow installation #1113
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
See further info in the following two issues: I'll close those issues and we'll track the work on this issue, since it's the first one raised. |
/area docs |
@ammarn911 is tackling this issue |
Status: PR #1469 has added an alpha banner to the Microk8s installation doc. There are still some questions to resolve - see comments in the PR, so I'll leave this issue open. |
A couple of thoughts about deploying kubeflow on workstations/appliances: There are a number of places in the kubeflow docs that start to outline how to deploy kubeflow in a single node cluster (and workstation/appliance) and finish in another set of instructions. This can be confusing. I tried to install kubeflow on a microk8s cluster and Ubuntu; I followed the instructions from https://master.kubeflow.org/docs/other-guides/virtual-dev/getting-started-multipass/. On this page, it may help to clarify the version of kubeflow that is available to install (and what components are in that package). Or, can you specify the version by a channel flag? How is Ambassador deployed or needed (routing)? Is there an explanation about Ambassador in the kubeflow docs? During a second microk8s+kubeflow installation/deployment, I used the kubeflow manifests (kfctl_k8s_istio.0.7.1.yaml) and deployed into microk8s. The deployment was successful, though, my cluster became unresponsive and I had difficulty removing kubeflow from the cluster. I read through the following pages: I would be interested in deploying a smaller set of kubeflow components that support a couple of samples/demos (deploy the examples with the prerequisite components). |
Thanks @kbhawkey that's super useful feedback. /cc @jlewi |
@ammarn911 I think we discussed this at the community meeting. I think you said you have testing in place? The other Canonical engineer mentioned that there is testing in this repo Is that covering the current installation guide I think the updated docs are now visible here What is the follow on work to #1469? |
See #1609 (comment) Do we need to add that to the instructions? Also it looks like there is a reference to Ambassador in the guide That needs to be updated. /cc @knkski |
Has this been fixed can we close it? |
I think the Microk8s/Multipass doc still needs some work. For example, it still refers to Ambassador: |
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. |
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
I need to use the latest mlpipelines released in 0.6.2 and am using a desktop to try it out. I have installed microk8s using the instructions at
https://www.kubeflow.org/docs/other-guides/virtual-dev/getting-started-multipass/
I used the latest executable for 0.6.2 with the following instructions.
I get the following error message :
Earlier the templates were using argoproj.io. Does something else need to be updated for the new profile to work ?
The text was updated successfully, but these errors were encountered: