question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

microk8s enable kubeflow fails on microk8s 1.21/beta

See original GitHub issue

The kubeflow addon fails to enable on microk8s 1.21/beta. The dex-auth pods are stuck in CrashLoopBackOff status with the following error message in the pod logs:

ubuntu@blanka:~$ microk8s kubectl logs dex-auth-5fcb9bc549-vjmhd -n kubeflow -c dex-auth
time="2021-03-27T18:42:37Z" level=info msg="config using log level: debug"
time="2021-03-27T18:42:37Z" level=info msg="config issuer: http://10.64.140.43.xip.io/dex"
failed to initialize storage: failed to inspect service account token: jwt claim "kubernetes.io/serviceaccount/namespace" not found

I also notice an error with the metadata-api pod:

ubuntu@blanka:~$ microk8s kubectl logs metadata-api-59c98cbdb9-qrwsz -n kubeflow
E0327 18:39:50.014738       1 register.go:68] Ignored unknown category "container" with type "workspace" in "http://github.com/kubeflow/metadata/schema/alpha/containers/workspace.json"
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0xe2419b]
[...]

The same command microk8s enable kubeflow works on microk8s channels 1.19 and 1.20, but not on the 1.21/beta channel.

I tried on both a Nvidia DGX A100 as well as on a ProLiant DL380 Gen10 and the result is the same.

ubuntu@blanka:~$ microk8s kubectl get pods -A | grep -v Running NAMESPACE NAME READY STATUS RESTARTS AGE ingress nginx-ingress-microk8s-controller-sm57t 0/1 CrashLoopBackOff 9 21m kubeflow dex-auth-5854d6666f-fc6fr 1/2 CrashLoopBackOff 6 12m kubeflow dex-auth-5fcb9bc549-vjmhd 1/2 CrashLoopBackOff 6 12m kubeflow metadata-api-59c98cbdb9-qrwsz 0/1 CrashLoopBackOff 7 14m

Additional information:

ubuntu@blanka:~$ snap list microk8s
Name      Version         Rev   Tracking   Publisher   Notes
microk8s  v1.21.0-beta.1  2085  1.21/beta  canonical✓  classic

ubuntu@blanka:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.2 LTS
Release:	20.04
Codename:	focal

inspection-report-20210327_183701.tar.gz

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:13 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
DavidSpekcommented, May 6, 2021

@mat-ej There is a fix stated here. Also ping @RFMVasconcelos

2reactions
davecore82commented, Mar 29, 2021

The following workaround lets me use Kubeflow and GPU with microk8s:

  1. sudo snap install microk8s --channel=1.20 --classic
  2. microk8s enable kubeflow
  3. sudo snap refresh microk8s --channel=1.21/beta
  4. microk8s enable gpu

There’s a few things required to enable gpu. See https://github.com/ubuntu/microk8s/issues/448#issuecomment-805122344 for details.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Issues - GitHub
The kubeflow addon fails to enable on microk8s 1.21/beta. The dex-auth pods are stuck in CrashLoopBackOff status with the following error ...
Read more >
Selecting a snap channel - MicroK8s
Selecting a snap channel. Microk8s is a snap deploying Kubernetes. The MicroK8s snap closely follows upstream Kubernetes, so understanding a bit about the ......
Read more >
Kubernetes API and Feature Removals In 1.22
The reason for all of these removals is that they have been superseded by a newer, stable (“GA”) API. Kubernetes 1.22, due for...
Read more >
Microk8s多机安装_明训的博客
由上可知问题原因,此时不用管这个问题,后面会解决。 container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message: ...
Read more >
Microk8s 1.21 fails to start after controlled cluster shutdown and ...
I have a 6-node microk8s cluster that's been running pretty well for several ... cluster Inspecting juju Inspect Juju Inspecting kubeflow Inspect Kubeflow....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found