Kubeflow: Unable to contact profile controller

[daniel-vera-g]

Opening the Kubeflow Dashboard Shows the error: Unable to contact profile controller and No Namespaces in the profile dropdown.

Steps to reproduce

export INSTALL_K3S_VERSION="v1.19.1+k3s1" && \
  k3ai cluster deploy --type k3s -n kubeflow-test && \
  k3ai plugin deploy -n kf-dashboard -t kubeflow-test

The k3s Version is to make sure that no errors regarding the CustomResourceDefinition come up, which is not supported in the latest Kubernetes version.

Checking the dashboard pod logs with k3s kubectl logs centraldashboard-7d496c59bb-gtpt4 --namespace kubeflowgets me:

> kubeflow-centraldashboard@0.0.2 start /app
> npm run serve


> kubeflow-centraldashboard@0.0.2 serve /app
> node dist/server.js

Initializing Kubernetes configuration
Unable to fetch Application information: 404 page not found

"k3s" is not a supported platform for Metrics
Using Profiles service at http://profiles-kfam.kubeflow:8081/kfam
Server listening on port http://localhost:8082 (in production mode)
Unable to contact Profile Controller Error: getaddrinfo ENOTFOUND profiles-kfam.kubeflow
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:66:26) {
  errno: 'ENOTFOUND',
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'profiles-kfam.kubeflow'
}

Nevertheless, the Cluster setup and plugin deployment process went without errors and all pods seem to run healthy.

I'm not sure, whether there is a pod missing or another component is needed.

[alefesta]

hmm, I think this relay on the dependencies that the dashboard is expecting to find... like the profile controller.
I'll review the upstream installation process and based on that (and if completely successful) I'll add the "dependencies" or, to say it better, the right order of components that need to be installed and configured.
This is part of the larger idea of being able to implement each KF component independently and slowly get to a point where all components are present as in the full KF installation... will add this as a bug to the 1.0.2 roadmap here
As usual thanks for reporting this!

[daniel-vera-g]

This is part of the larger idea of being able to implement each KF component independently and slowly get to a point where all components are present as in the full KF installation... will add this as a bug to the 1.0.2 roadmap here As usual thanks for reporting this!

Thanks for the fast response!
I'm curious about the last part you mentioned. Doing a full KF installation allows to access the different components directly from the Dashboard.
As I could see, currently K3ai published each component(Plugin) on another Port/Endpoint.
When I for example want to access the Pipelines from the Dashboard, this is not possible as they're not on the Path the Dashboard expects it to be.
Did I understand you correctly that accessing the components directly from the Dashboard would be possible with the idea you mentioned to the end ?