Get started

charm
,
22

ubuntu22.04

I just followed the tutorial.

All pods work normally, but the following error occurs.

스크린샷 2023-11-24 19-44-05
스크린샷 2023-11-24 19-44-051402×273 65.3 KB

1 Like
23

Hey @kkhe56, looks like something is going on with the MySQL databases.

With a quick look the root problems seem to be katib-db and kfp-db, which are using the mysql-k8s charms. The other charms then are blocked because kfp-api is waiting for the database.

We’ll need to further dig into your environment to understand why the DB charms are in “unknown” state. Could you follow up with an issue in https://github.com/canonical/bundle-kubeflow where the team can follow up and ask for more technical details?

1 Like
24

I think that this can now all be replaced by just running juju bootstrap microk8s, as Juju can automatically connect itself to microk8s.

The 3.1/stable channel is now only available with strict confinement, and will spit out a warning if you try to install it with --classic:

itrue@kubeflow:~$ sudo snap install --classic --channel 3.1/stable juju
Warning: flag --classic ignored for strictly confined snap juju

juju (3.1/stable) 3.1.7 from Canonical✓ installed
25

This should be --watch 5s, rather than -watch 5s

1 Like
26

hi there,

   kindly advise how to create multiple users login in kubeflow dashboard in juju kubeflow ,coz by default its coming with static user&pass , we required multiple user profile for dev teams.so please support us .
27

This should be updated to use Juju 3.4 with sudo snap install juju --classic --channel=3.4/stable

It’s the only version of Juju for which I was able to get Kubeflow 1.8 to work while following this

28

There is a typo. This should be used:

sudo snap install kubectl --classic

29

Hi, I configured the dashboard access but I’m unable to access it, the site doesn’t load. And juju config oidc-gatekeeper public-url=http://$EXT_IP.nip.io errors out saying ERROR parsing settings for application: unknown option "public-url". I didn’t find the above command in this guide but found it in the guide which uses Kubeflow 1.8 just to see if this works.

30

I have the same issues, but I also noticed that part is not in the getting started guide anymore

31

Hi @lukas and @shrishtikarkera!

The public-url option has been removed from oidc-gatekeeper, hence the message:

ERROR parsing settings for application: unknown option "public-url"

This option was left in dex-auth for compatibility reasons, but it should not be used anymore.

To help debug, please let us know if:

  1. The dex-oidc-config relation between dex-auth and oidc-gatekeeper exists:
# This should show two relations with `oidc-gatekeeper`
juju status dex-auth --relations
  1. There is relation data in oidc-gatekeeper:
$ juju show-unit oidc-gatekeeper/0
oidc-gatekeeper/0:
...
  - relation-id: 48
    endpoint: dex-oidc-config
    related-endpoint: dex-oidc-config
    application-data:
      issuer-url: http://dex-auth.kubeflow.svc:5556/dex # <--- this should exist
  1. You are using a Dex connector, please check this guide

Just FYI, the charms in CKF 1.9 should configure themselves to allow access to the dashboard, that is why it has been removed from the getting started guide. If you are still having issues after the debugging I suggested before, do you mind providing logs or messages you get? Preferably in our issue tracker.

32

Hey, thanks for the help. Unfortunately when changing the issuer I run into more issues: https://github.com/canonical/bundle-kubeflow/issues/1028

33

Alright, thanks for the report. We’ll evaluate it today. Let’s continue the discussion over there.

1 Like
34

Hello again, because of the strict confinement I ran in further issues.

Is it possible to setup charmed kubeflow on microk8s 1.29 using classic confinement instead?