[TASK] Containerize frontend component

[andyatmiami]

Description

We want to be able to run the frontend component as a container. Presently, the only means to run the frontend is locally via command-line. Ultimately, we need/want frontend to be a workload resource running within k8s. To get started in realizing that goal - the first thing that must happen is defining a Dockerfile that supports containerizing the application.

Some examples of Dockerfile

• kubeflow/notebooks backend
  • https://github.com/kubeflow/notebooks/blob/notebooks-v2/workspaces/backend/Dockerfile
• kubeflow/model-registry ui
  • https://github.com/kubeflow/model-registry/blob/main/clients/ui/Dockerfile

Obviously the kubeflow/model-registry example is slightly more relevant - as it demonstrates containerizing a NodeJS application similar to our frontend. However, please note in model-registry the "bff" ( backend ) component is packaged with the ui client. Whereas in kubeflow/notebooks - the community preference is that our frontend is a separate container from the backend.

Acceptance Criteria

• docker and/or podman can produce a container image of the frontend component
• The resulting container image can be run with a container engine (podman / docker ) and be at parity with functionality available when running locally

[andyatmiami]

/area v2
/area frontend

[noalimoy]

/assign