central-dashboard: Configure build_version dynamically through ENV var

[orfeas-k]

/kind feature

Context
At the moment, KF's build version in the dashboard is defined only during build time. More specifically and as explained thoroughly in this issue #25, it is not even defined and thus it is constantly dev_local.

For some more thorough technical context, in theory, it can also be defined during runtime through a custom resource that doesn't exist anymore in KF (here with the callback trace being 1, 2 and 3).

Feature
Configure the build_version dynamically during runtime by using a deployment's ENV variable.

Why you need this feature:
This will allow for anyone to be able to configure the build_version value in their distribution without having to rebuild the image.

Describe the solution you'd like:
The solution can be inspired at a great extent what has been done for centraldashboard-angular component in kubeflow/kubeflow#6918. The changes that really interest us are the ones in backend k8s_service.ts file. We could also consider splitting build_version to buildVersion, buildId and buildLabel but that's optional. Then, we may have to implement the new ENV variables here, although if we use kubeflowVersion, changing only where k8s gets this variable from may be enough.

[andreyvelich]

/transfer dashboard

[google-oss-prow]

@orfeas-k: The label(s) kind/feature cannot be applied, because the repository doesn't have them.

In response to this:

/kind feature

Context
At the moment, KF's build version in the dashboard is defined only during build time. More specifically and as explained thoroughly in this issue #25, it is not even defined and thus it is constantly dev_local.

For some more thorough technical context, in theory, it can also be defined during runtime through a custom resource that doesn't exist anymore in KF (here with the callback trace being 1, 2 and 3).

Feature
Configure the build_version dynamically during runtime by using a deployment's ENV variable.

Why you need this feature:
This will allow for anyone to be able to configure the build_version value in their distribution without having to rebuild the image.

Describe the solution you'd like:
The solution can be inspired at a great extent what has been done for centraldashboard-angular component in kubeflow/kubeflow#6918. The changes that really interest us are the ones in backend k8s_service.ts file. We could also consider splitting build_version to buildVersion, buildId and buildLabel but that's optional. Then, we may have to implement the new ENV variables here, although if we use kubeflowVersion, changing only where k8s gets this variable from may be enough.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[juliusvonkohout]

/lifecycle frozen