kubeflow: Can't install >v0.1.3 KubeFlow to Microk8s

I’ve followed instruction of Microk8s and have installed 0.1.3 successfully.

But when I’m trying to install newer versions 0.2.7 or 0.3.1 they won’t work.

I’ve got:

$ VERSION=v0.3.1 /kubeflow/install-kubeflow.sh
namespace/kubeflow created
INFO Using context “microk8s” from kubeconfig file “/snap/microk8s/current/client.config”
INFO Creating environment “default” with namespace “default”, pointing to cluster at address “http://127.0.0.1:8080”
INFO Generating ksonnet-lib data at path ‘/home/multipass/my-kubeflow/lib/v1.12.0’
INFO Retrieved 38 files
INFO Retrieved 9 files
ERROR resolve registry library: GET https://api.github.com/repos/kubeflow/kubeflow/contents/kubeflow/tf-job?ref=c456ceec089675e7f5c4a7494fb0f7ce875fe062: 404 Not Found []

$ VERSION=v0.2.7 /kubeflow/install-kubeflow.sh
namespace/kubeflow created
INFO Using context “microk8s” from kubeconfig file “/snap/microk8s/current/client.config”
INFO Creating environment “default” with namespace “default”, pointing to cluster at address “http://127.0.0.1:8080”
INFO Generating ksonnet-lib data at path ‘/home/multipass/my-kubeflow/lib/v1.12.0’
INFO Retrieved 33 files
INFO Retrieved 5 files
ERROR resolve registry library: GET https://api.github.com/repos/kubeflow/kubeflow/contents/kubeflow/tf-job?ref=4ffd0a5aa97cea1eddcab185fd33da08e9efad8a: 404 Not Found []

Is Microk8s still in business or I should switch to Minikube to get newer Kubeflow?

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 15 (2 by maintainers)

Most upvoted comments

@hyzhak, the plan is to have the fix https://github.com/snapcore/snapd/pull/5739 released so that you will not need any special scripts to deploy on microk8s. I do not have an ETA for that yet, I need to get back to you on this.

ktsakalozos on Oct 26, 2018

Hi @hyzhak ,

microk8s is still in business. Yes you can use microk8s outside multipass as long as you are on ubuntu, just do a sudo snap install microk8s --classic. The kubeflow installation instructions give you v0.1.3 because we are waiting on a bug fix to be released(*).

If you want to deploy a v0.2 kubeflow you will need to use a jupyterHubImage that lives in kjackal/jupyterhub-k8s:v0.9.2 essentially this means you have to ks param set kubeflow-core jupyterHubImage kjackal/jupyterhub-k8s:v0.9.2. If you do not want to wait for the above fix to be released, here is the v0.2.0 deployment script you have to run after having ks and microk8s installed.

#!/usr/bin/env bash
set -eux

sudo snap alias microk8s.kubectl kubectl
mkdir -p ~/.kube
microk8s.config > ~/.kube/config
microk8s.enable dns dashboard storage
sudo iptables -P FORWARD ACCEPT

KUBEFLOW_VERSION=${KUBEFLOW_VERSION:-v0.2.2}
wget https://raw.githubusercontent.com/kubeflow/kubeflow/v${KUBEFLOW_VERSION}/scripts/deploy.sh
cat ./deploy.sh | awk '{if ($n ~ "# Apply the components generated") {print "ks param set kubeflow-core jupyterHubImage kjackal/jupyterhub-k8s:v0.9.2"; print $n} else print $n}' > deploy-kf.sh
bash ./deploy-kf.sh

The fix on https://github.com/snapcore/snapd/pull/5739 is already merged into the microk8s stack and is about to be released.

ktsakalozos on Oct 26, 2018