[Proposal] Add Netlify for Deploy Previews in CI/CD Pipeline

[RONAK-AI647]

While exploring ways to extend the CI/CD pipeline for the Dashboard repository and wanted to ask about the possibility of integrating Netlify for deploy previews.

Deploy previews can:

• Help reviewers visualize frontend changes before merging
• Catch rendering/UI bugs early in the pull request phase
• Provide a smoother contribution experience for both maintainers and contributors

Possible Clarification/Questions from maintainers:

1. Is the use of the Netlify GitHub App permitted for this repository?
2. If not, is a deploy pipeline using the Netlify CLI inside GitHub Actions (without the app) acceptable?

Alternative Idea if Netlify app faces restriction:
** We can set up deploy previews using the Netlify CLI directly in Actions
Or use another deployment service, depending on your guidance .

**

[RONAK-AI647]

/assign

[JesseStutler]

Good catch. But I think this CI may be more complicated than simply deploying a dashboard, because the dashboard needs to connect to a k8s cluster (such as Kind), not just display the frontend page

[RONAK-AI647]

@JesseStutler , I am aware about that and the issue of Dockerizing dashboard mentions this the dashboard needs to connect to a k8s cluster .What if I design a CI pipeline with something likekind+ Docker Compose +netlifyto frontend previews.

[JesseStutler]

@JesseStutler , I am aware about that and the issue of Dockerizing dashboard mentions this the dashboard needs to connect to a k8s cluster .What if I design a CI pipeline with something likekind+ Docker Compose +netlifyto frontend previews.

Why do we need to use docker-compose? The dashboard can directly build the image and deploy in the kind cluster, just using deployment/volcano-dashboard.yaml

[RONAK-AI647]

We need a docker-compose because:

1. It will simplify the local development (no kubernetes setup needed),quick testing, and onboarding new contributors.

2)Right now , we have a docker file for frontend and one docker file for backend . docker-``compose.yml integrates both of them .(e.g., frontend + backend + DB + volumes + networks). This defines how to run multi-container setups. And yes it turns those 4 commands for local setup to just one.

3. One more potential issue I faced was "failing of the port forwarding" when using general npm dev method , but docker-compose.yml gives it a solution thats ports are exposed properly using its internal networking.

4. Surely in future , dashboard will turn into a bigger repo , this makes the project scalable and mainatainable .

There were alraedy issues opened about it which was approved by @Monokaix @maverick.
I’ll respect whichever direction you choose. I just wanted to share the idea in case it could be helpful for the future growth and accessibility of the project.