Fix single binary config

[Yicheng-Lu-llll]

Describe your changes

The existing flyte_local.yaml configuration file has fallen out of date, causing issues when running single binaries. The standard process ideally looks like this:

# Start a k3s cluster, create pods for postgres, minio.
flytectl demo start --dev
# Start all backends (flyteidl, flyteadmin, flyteplugins, flytepropeller) and HTTP Server in a single binary 
sudo make compile
flyte start --config flyte_local.yaml

This PR introduces necessary updates to the flyte_local.yaml configuration file.

Checks

flytectl demo start --dev
# 👨‍💻 Flyte is ready! Flyte UI is available at http://localhost:30080/console 🚀 🚀 🎉 
# ❇️ Run the following command to export demo environment variables for accessing flytectl
#         export FLYTECTL_CONFIG=/root/.flyte/config-sandbox.yaml 
# 🐋 Flyte sandbox ships with a Docker registry. Tag and push custom workflow images to localhost:30000
# 📂 The Minio API is hosted on localhost:30002. Use http://localhost:30080/minio/login for Minio console

sudo make compile
flyte start --config flyte_local.yaml

# running a hello_world sample from flytesnacks
pyflyte run --remote core/flyte_basics/hello_world.py my_wf
# Go to http://localhost:30080/console/projects/flytesnacks/domains/development/executions/f40d94cefb5e74fe6b09 to see execution in the console.

pyflyte run --remote core/flyte_basics/deck.py wf
# Go to http://localhost:30080/console/projects/flytesnacks/domains/development/executions/f39a9c56828e54bb09be to see execution in the console.

Able to run the task

Able to see the deck:

Able to see the kubernetes logs:

[Yicheng-Lu-llll]

Refer to how the current flytectl works: https://github.com/flyteorg/flytectl/blob/0cb2bfaf436a09d58c1ae9c1389eacb6eab8a856/pkg/docker/docker_util.go#L30

[wild-endeavor]

Is it this variable or SandboxKubeconfig that's used in flytectl demo? Let's keep whatever is used for demo not sandbox.

[wild-endeavor]

otherwise looks good.

[Yicheng-Lu-llll]

It is also used for flytectl demo.

startDemoCluster -> sandbox.StartDemoCluster -> StartCluster -> UpdateLocalKubeContext.

UpdateLocalKubeContext copies the kubeconfig to $HOME/.flyte/sandbox/kubeconfig

[Yicheng-Lu-llll]

Running kubectl get svc -A :

flyte         flyte-sandbox-postgresql             NodePort    10.43.143.68    <none>        5432:30001/TCP                  2m4s

[Yicheng-Lu-llll]

Running kubectl get svc -A :

flyte         flyte-sandbox-minio                  NodePort    10.43.93.113    <none>        9000:30002/TCP,9001:32697/TCP   2m4s

[pingsutw]

FYI @ByronHsu

[jeevb]

I’ve been using this one: https://github.com/flyteorg/flyte/blob/master/flyte-single-binary-local.yaml

Perhaps we can consolidate and clean up?

[Yicheng-Lu-llll]

@jeevb I didn't notice the flyte-single-binary-local.yaml until you told me how to solve the webhook issues. In this case, do you mind I just remove flyte_local.yaml in this PR since it does not fit flytectl demo start --dev any more?

[jeevb]

@jeevb I didn't notice the flyte-single-binary-local.yaml until you told me how to solve the webhook issues. In this case, do you mind I just remove flyte_local.yaml in this PR since it does not fit flytectl demo start --dev any more?

It might still be valid for the legacy sandbox. We do plan on deprecating it , and we can clean it up then?