Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[frontend] KFP version is unknown and the cluster information is missing in the KFP UI left sidenav #11573

Open
devina-ekawati opened this issue Jan 31, 2025 · 1 comment

Comments

@devina-ekawati
Copy link

Environment

  • How did you deploy Kubeflow Pipelines (KFP)?
    Google Kubernetes Engine (GKE), standalone KFP

  • KFP version:
    2.4.0

Steps to reproduce

Open the KFP dashboard then check the KFP version and cluster information in the left sidenav (refer to the screenshots below)
Image

Expected result

The KFP UI left sidenav show 2.4.0 as the version and show the cluster information correctly.

Materials and Reference

To get the value of the KFP version, the frontend calls /apis/v1beta1/healthz. When I tried to call this API, it returns:

{
    "buildDate": "",
    "frontendCommitHash": "",
    "frontendTagName": "",
    "apiServerReady": true,
    "apiServerCommitHash": "unknown",
    "apiServerTagName": "unknown",
    "apiServerMultiUser": false,
    "multi_user": false
}

After further reading, it seems that those values are populated from COMMIT_SHA and TAG_NAME, which are read from environment variable (ref). These environment variables are set inside the Dockerfile of the kfp-api-server.

For the cluster metadata, I got GKE metadata endpoints are disabled. error message when inspecting the UI using browser developer console. It worked as expected in the previous version (2.3.0). During the version upgrade, I also didn't make any changes on the cluster.


Impacted by this bug? Give it a 👍.

@izuku-sds
Copy link

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants