DomFleischmann

There is a workaround for this bug, please delete the `oidc-gatekeeper` pod and wait for a new one to spin up. That should fix your issue.

Yes, you will have to access the dashboard through the IP of the istio-ingressgateway and `nip.io` which in your case would be this url: `10.64.140.43.nip.io`

@bmccord2 There are some known issues with the nvidia operator and microk8s 1.21 you can try with microk8s 1.20 which uses the older and a bit more limited nvidia operator....

For Canonical's Charmed Kubeflow > Are you planning on having your distro ready in sync with the KF 1.6 release? Yes > Will you participate by testing your distro during...

I've hit this issue today while testing 1.6 on microk8s. The pods affected were: katib-controller, kubeflow-profiles, kfp-api and kfp-persistence. @mstopa 's workaround did fix it, but I'm wondering if we...

Hi @kubeflow/wg-automl-leads , Before the [manifest testing](https://github.com/kubeflow/community/blob/master/releases/handbook.md#manifests-testing-1-week) on Wednesday, Feb 9th, the release team is planning on cutting another RC to use for the testing. Based on a previous communication,...

Hi @kubeflow/wg-training-leads , Before the [manifest testing](https://github.com/kubeflow/community/blob/master/releases/handbook.md#manifests-testing-1-week) on Wednesday, Feb 9th, the release team is planning on cutting another RC to use for the testing. Based on a previous communication,...

Hello @camille-rodriguez have you encountered this issue again in 1.6? If not I will proceed and close this issue.

This is a known upstream [bug](https://github.com/kubeflow/kubeflow/issues/6056) we are trying to get it fixed for the next release.

This is now fixed in Kubeflow 1.6 both upstream and on our distribution. I would encourage anyone who is still hitting this to upgrade to it.