Deploy to the Cloud#


Make sure you have Docker and Docker Daemon is running.


Being connected to a VPN may cause problems downloading the image.

Setup and Configuration#

First, install flytectl.

Then you can setup a local Flyte Sandbox cluster or configure flytectl to use a pre-provisioned remote Flyte cluster.


Learn how to deploy to a Flyte Cluster using the Deployment Guides.

To start the Flyte Sandbox, run:

flytectl sandbox start --source .


The '.' represents the current directory, which would be my_flyte_project in this case.

If you’re having trouble with starting the sandbox cluster, refer to Troubleshooting Guide.

Build & Deploy Your Application to the Cluster#

Flyte uses Docker containers to package the workflows and tasks, and sends them to the remote Flyte cluster. Therefore, there is a Dockerfile already included in the cloned repo. You can build the Docker container and push the built image to a registry.

Since flyte-sandbox runs locally in a Docker container, you do not need to push the Docker image. You can combine the build and push step by simply building the image inside the Flyte-sandbox container. This can be done using the following command:

flytectl sandbox exec -- docker build . --tag "my_flyte_project:v1"


Why are we not pushing the Docker image? To understand the details, refer to Sandbox Deployment.

Next, package the workflow using the pyflyte cli bundled with Flytekit and upload it to the Flyte backend. Note that the image is the same as the one built in the previous step.

pyflyte --pkgs flyte.workflows package --image "my_flyte_project:v1"

Upload this package to the Flyte backend. We refer to this as registration. The version here v1 does not have to match the version used in the commands above, but it is generally recommended to match the versions to make it easier to track.


Note that we are simply using an existing project flytesnacks and an existing domain development to register the workflows and tasks. It is possible to create your own project and configure domains. Refer to Control Plane to understand projects and domains.

flytectl register files --project flytesnacks --domain development --archive flyte-package.tgz --version v1

Finally, visualize the registered workflow in a web browser.

flytectl get workflows --project flytesnacks --domain development flyte.workflows.example.my_wf --version v1 -o doturl

You can also view the workflow as a strict digraph on the command line.

flytectl get workflows --project flytesnacks --domain development flyte.workflows.example.my_wf --version v1 -o dot

Execute on the Flyte Cluster#

Launch and monitor from the CLI using Flytectl. More details can be found here.

Generate an execution spec file.

flytectl get launchplan --project flytesnacks --domain development flyte.workflows.example.my_wf --latest --execFile exec_spec.yaml

Create an execution using the exec spec file.

flytectl create execution --project flytesnacks --domain development --execFile exec_spec.yaml

You should see an output that looks like:

execution identifier project:"flytesnacks" domain:"development" name:"<execution_name>"

Monitor the execution by providing the execution name from the create execution command.

flytectl get execution --project flytesnacks --domain development <execution_name>

Alternatively, you can FlyteConsole to launch an execution.

Visit http://localhost:30080/console on your browser

Then use the FlyteConsole to launch an execution:

A quick visual tour for launching a workflow and checking the outputs when they're done.


We’ve successfully packaged your workflow and tasks and pushed them to a Flyte cluster! 🎉 Next, let’s learn how to iterate on and re-deploy our Flyte app.

Total running time of the script: ( 0 minutes 0.000 seconds)

Gallery generated by Sphinx-Gallery