So I created a sandbox using:

flytectl sandbox start --source .

. After doing that, I can access to Flyte UI. However, after stopping the container, I tried to run

flytectl sandbox start --source .

to resume the existing sandbox cluster, but I can't access to Flyte UI. Here is the specific outputs I got:

➜ flytectl sandbox start                                       
🧑‍🏭 Bootstrapping a brand new flyte cluster... 🔨 🔧
delete existing sandbox cluster [y/n]: n
Existing details of your sandbox👨‍💻 Flyte is ready! Flyte UI is available at <http://localhost:30081/console> 🚀 🚀 🎉 
Add KUBECONFIG and FLYTECTL_CONFIG to your environment variable 
export KUBECONFIG=$KUBECONFIG:/home/khuyen/.kube/config:/home/khuyen/.flyte/k3s/k3s.yaml 
export FLYTECTL_CONFIG=/home/khuyen/.flyte/config-sandbox.yaml

I wonder what is the best way to resume the existing cluster?

Hi community! I'm trying to run a dummy python job on a 🧱 job cluster (_new_cluster_) using

pyflyte

. For some reason, when I add

policy_id

to the cluster config, the Flyte job fails with an error like this:

Dear Flyte Community, I wanted to share some exciting news with all of you. While it may not be directly related to Flyte, I started Union, a venture aimed at supporting Flyte development and collaborating with the incredible community of individuals like yourselves. This is why the recent announcement of Union AI raising significant funding is of utmost importance for our Flyte community. We have witnessed Flyte's widespread adoption and the increasing contributions from passionate individuals. Among these contributors, Union AI stands out as one of the top supporters. We are committed to nurturing this community and ensuring its everlasting success. With this goal in mind, I am pleased to share that we have raised $19.1 million for Union, a substantial portion of which will be dedicated to enhancing Flyte and making it the world's best Orchestration platform. You can find more details about this exciting development here. I am immensely grateful for your unwavering support and love. Together, let us continue working hand in hand to empower our end users, relieving them of infrastructure worries, and enabling companies worldwide to harness the power of Flyte. With heartfelt appreciation, Ketan

FYI - flytekit 1.5.0 seems to have dependency conflicts -

Could not find a version that matches fsspec==2023.3.0,==2023.4.0,>=2021.10.1,>=2023.3.0

Hello guys I'm having a new error. I packaged a project to Docker hub. And then used FlyteRemote to register the workflow to a remote Flyte cluster on AWD EKS -- adding the IMAGE_STR. However, when I fetch and execute the workflow, it raises a

ModuleNotFoundError

. What could I be doing wrong please?

Do we have to change the default USER for spark tasks like above?

hi team, the documentation states that subworkflows execute within context of the parent workflows (here). What are the implications of that?

The loadbalancer (metallb) successfully provided an IP address, and console is available through that address. Here is flyte config.yaml

admin:
  # For GRPC endpoints you might want to use dns:///flyte.myexample.com
  endpoint: dns:///192.168.111.220
  insecure: true
logger:
  show-source: true
  level: 0

Here is a screenshot of the console:

Hi, is there a way to use a different ingress service? I’m using

emissary-ingress

and I was wondering if you had a reference implementation for that instead of using Amazon Loadbalancer Ingress Controller?