Revamp deployment files to get UI in one container

[lucferbux]

Description

Refactor the architecture to serve everything in the same container

How Has This Been Tested?

I need to test kubeflow integration first

For local kind cluster just run make kind-deployment and test that it's working.

Merge criteria:

• All the commits have been signed-off (To pass the DCO check)

• The commits have meaningful messages; the author will squash them after approval or in case of manual merges will ask to merge with squash.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work.
• Code changes follow the kubeflow contribution guidelines.

If you have UI changes

• The developer has added tests or explained why testing cannot be added.
• Included any necessary screenshots or gifs if it was a UI change.
• Verify that UI/UX changes conform the UX guidelines for Kubeflow.

[Griffin-Sullivan]

Need to test. That was a lot of work nice job @lucferbux!

[lucferbux]

Ok so tested in these environments:

• Local development
• Build kind deployment (automated script)
• Kubeflow deployment

We've removed docker-compose and improve documentation to display all the configurations. Also, I've tested github actions and its working just fine:

cc @rareddy @tarilabs

[Griffin-Sullivan]

Tested for local dev, local kind deployment, and kubeflow deployment. Nice work @lucferbux!

[Griffin-Sullivan]

All good for me!

[tarilabs]

• per understanding this refactor from 2 images, 2 Pods to make BFF use separate from UI optionally,
• not moving to 1 Pod 2 containers as it would make it tricky to support option of BFF without UI
• and move to 1 Pod 1 image with both BFF and F/E, so to make option in the deployment to avoid/skip UI capability

/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Griffin-Sullivan, tarilabs

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tarilabs]

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

[Griffin-Sullivan]

/lgtm