Kubeflow can't be enabled after Nov. 2020 microk8s releases (always timeout)
See original GitHub issuePlease run microk8s inspect
and attach the generated tarball to this issue.
Kubeflow can’t be enabled after microk8s Nov. 2020 releases. https://ubuntu.com/tutorials/deploy-kubeflow-ubuntu-windows-mac#3-install-microk8s
Tried versions, latest/edge, 1.19/edge, 1.18/edge, latest/stable, 1.19/stable, 1.18/stable
All timeout since the week of 11/16/2020.
Error message: … Waited 330s for operator pods to come up, 1 remaining. Operator pods ready. Waiting for service pods to become ready. Kubeflow could not be enabled: error: timed out waiting for the condition on pods/oidc-gatekeeper-7dbfc94964-r89cg Command ‘(‘microk8s-kubectl.wrapper’, ‘wait’, ‘–namespace=kubeflow’, ‘–for=condition=Ready’, ‘pod’, ‘–timeout=30s’, ‘–all’)’ returned non-zero exit status 1 ********************************* cause: kubeflow pod/oidc-gatekeeper-7dbfc94964-r89cg 0/1 CrashLoopBackOff 34 152m (this service refuse to come up)
Inspecting Certificates Inspecting services Service snap.microk8s.daemon-cluster-agent is running Service snap.microk8s.daemon-containerd is running Service snap.microk8s.daemon-apiserver is running Service snap.microk8s.daemon-apiserver-kicker is running Service snap.microk8s.daemon-control-plane-kicker is running Service snap.microk8s.daemon-proxy is running Service snap.microk8s.daemon-kubelet is running Service snap.microk8s.daemon-scheduler is running Service snap.microk8s.daemon-controller-manager is running Copy service arguments to the final report tarball Inspecting AppArmor configuration Gathering system information Copy processes list to the final report tarball Copy snap list to the final report tarball Copy VM name (or none) to the final report tarball Copy disk usage information to the final report tarball Copy memory usage information to the final report tarball Copy server uptime to the final report tarball Copy current linux distribution to the final report tarball Copy openSSL information to the final report tarball Copy network configuration to the final report tarball Inspecting kubernetes cluster Inspect kubernetes cluster Inspecting juju Inspect Juju Inspecting kubeflow Inspect Kubeflow
Building the report tarball Report tarball is at /var/snap/microk8s/1821/inspection-report-20201119_172119.tar.gz ubuntu@ip-172-31-52-231:~$ cd /var/snap/microk8s/1821/
inspection file attached.
Need to know which microk8s still working with Kubeflow. Thanks. inspection-report-20201119_172119.tar.gz
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top GitHub Comments
Yes it is fixed now after build 1826. sudo snap install microk8s --classic --channel=latest/edge I just tried with build 1827 (latest) up successfully. Also changed disk to 80G instead of 60G.
Thank you.
@knkski Yes working no issue with your latest build, v1.20.2 2021-02-01 (1997). All KF services coming up cleanly. Be able to access KF dashboard and create new notebook server. Thx.