Integration with volcano-global

[joeyearsley]

I've tried running this with volcano-global but can't see any jobs from the primary host, only from individual member clusters. Does this work with volcano-global to provide a single dashboard of all jobs across the cluster?

If not, is it ever planned to?

[Monokaix]

That's a good point: )
The volcano dashboard use InClusterConfig to talk to apiserver, so it will only show jobs from where it connects to, a workaround is setting the KUBECONFIG env to the karmada apiserver, and it's also reasonable to set a param flag in the future version.

[Monokaix]

/good-first-issue

[volcano-sh-bot]

@Monokaix:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.

[Shrutim1505]

Is this issue already figured out?? @Monokaix
or should i work on it ??

[Monokaix]

Is this issue already figured out?? @Monokaix or should i work on it ??

Yeah and welcome!

[RONAK-AI647]

assign it to me plzz @Monokaix

[RONAK-AI647]

Would like to connect the wholesome of open issue together :

There are issues open on

1. Integration with volcano-global Integration with volcano-global #9
2. Dockerize Volcano Dashboard Dockerize Volcano Dashboard #90
3. Introduction of Docker compose Introduction of Docker compose #12
4. [BUG] Port forwarding fails [BUG] Port forwarding fails #89

All these issues somewhere revolve around the same logic:
If we dokerize the volcano Dashboard with docker-compose.yml , we will likely see the following outcomes:

• simplify service orchestration and deployment.
• access the frontend and backend of dashboard via ports 8080 (frontend) and port 3001 (backend). Users to set up the development environment more easily with a single command.
• Used Minikube to run Kubernetes locally.
• Mounted your ~/.kube/config file (or Minikube’s kubeconfig path) into Docker so the app (e.g., backend or dashboard) could:
• And the port forwarding will not fail with docker setup method( I have tested with docker)

Connect to Kubernetes from outside the cluster.

Reference this screenshot from @Monokaix , which explains the wirking of dashboard using " InClusterConfig" to access the api server and how KUBECONFIG will work like a map to the karmada apiserver.