Hi @Moula , thanks for reporting this. You can resolve this issue by running juju trust knative-eventing --scope=cluster
, and the same for knative-serving
. We have merged the fix for that already, you should not run into this issue in latest kubeflow (1.7/beta revision 333). Please let us know if you find any other issue.
Just confirmed that latest (revision 333) deploys all components: juju deploy kubeflow --channel 1.7/beta --trust
I have successfully installed charmed-kubeflow on GCP but I donât have access to It, how do I have access to it? (newby) I did run the following code already but no success:
juju config dex-auth public-url=http://<IP address>
juju config oidc-gatekeeper public-url=http://<IP address>
with my istio-ingressgateway ClusterIP
Hey!
Iâve never tried myself on GCP, so Iâm guessing a bitâŠ
Iâm guessing youâve done the Configure the components and login to charmed kubeflow sections of the tutorial, but no luck? Theres an âexpand to troubleshootâ under that section too that might help.
Are you trying to access the dashboard from your local machine but it is hosted on the GCP machine? You might need something like a SOCKS proxy to help out. This section talks about that.
Hope these help. Please let me know!
With my deployment I found a bug in the UI interface of kubeflow. The âLOGOUTâ button never works!!! I tried with 3 different deployments, the bug is still there. Capture dâĂ©cran du 2023-03-27 10-50-19|690x515
Hi @Moula,
This has been a very long-standing bug, but with the charmed kubeflow 1.7 stable release it should be fixed!