[TASK] Define k8s workload manifest for frontend component

[andyatmiami]

🛑 Blocked by #392

Description

Presently, the only way to run the front component is by invoking it locally on your machine. We must be able to run this component on kubernetes.

⚠ Tooling to enable developers working on the component to easily deploy / undeploy the workload will be tracked in a subsequent ticket.

• Presently the frontend component does not have a Makefile defined

Acceptance Criteria

• Implementation is kustomize-compatible (but no overlays directory need necessarily be defined)
  • See controller folder structure for a (more complicated) example
  • manager subfolder might be a better specific/representative example
• Workload can be successfully deployed to k8s (enter READY state) using kubectl
• Workload can be configured to connect to a Notebooks 2.0 backend workload
  • For now, can assume backend running in same cluster/namespace - but not this can (will?) change in the future

[andyatmiami]

/area v2
/area frontend

[noalimoy]

/assign