fix: serve static assets with nginx instead of npm start

[KUNDAN1334]

Motivation

Current Dockerfile uses npm start (Node.js server) in production:

• 900MB image size (node:16-alpine + 1604 npm packages)
• Unnecessary runtime (webpack already builds static assets)
• Larger attack surface (old Node.js deps with 154 vulns)

Changes

• Dockerfile: Replace Node serve → nginx static serve

  FROM nginx:1.25-alpine AS serve  # ~10MB vs 900MB
  COPY --from=build /centraldashboard/public /usr/share/nginx/html
  

Closes #211

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign kimwnasptd for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• components/centraldashboard/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[christian-heusel]

Did you test those changes by running the application?

[KUNDAN1334]

Hey @christian-heusel

Thanks for review! Verified webpack → nginx flow:

Local verification:

npm run build → Static assets generated ✓
app.bundle.js (1.34MB)
app.css (31.5 KiB)
public/index.html + assets/

[christian-heusel]

@KUNDAN1334 nice, thats already good to know! 🤗 please also test the UI itself and not just the outputs of the CLI tools 👍🏻

[KUNDAN1334]

@christian-heusel ! Full UI test complete on Mac M4 + Kind v1.35.0

Test Environment:
Kind cluster (minimal): kf-test-control-plane
nginx image: localhost:5000/centraldashboard:nginx-test (65MB vs ~900MB original)
Deployment: centraldashboard → 1/1 Running (6m+)
Port-forward: localhost:8082

Note: Empty panels expected in standalone deployment - only centraldashboard running (no Notebooks/Pipelines backend services deployed). Core UI + nginx static serving verified

[KUNDAN1334]

any update @christian-heusel ??