Skip to content

_index.md

Latest commit

 

History

History
52 lines (44 loc) · 2.52 KB

_index.md

File metadata and controls

52 lines (44 loc) · 2.52 KB
Raw
title Platform deployment
description Deploy Flyte to your own Kubernetes cluster with the flyte-binary or flyte-core Helm chart.
icon server
variants +flyte -union
weight 5
top_menu true

Platform deployment

This section covers how to deploy Flyte to your own Kubernetes cluster.

Flyte ships as a single unified binary that bundles the runs service, the task/actions controller, the data proxy, and the app service, served alongside the Flyte web console. You point it at three things you provision yourself (a Kubernetes cluster, a PostgreSQL database, and an object store).

Two Helm charts deploy that binary. The flyte-binary chart runs every component in one Deployment that you scale vertically — the right choice for most installs. The flyte-core chart runs one Deployment per component, for when you need to scale, schedule, or roll them out independently.

[!INFO] Try Flyte Devbox in your browser

You can deploy Flyte Devbox, a light-weight Flyte cluster, locally using the Flyte Devbox.

If you want to try it without installing anything on your local machine or cloud environment, create a Flyte Devbox in Github Codespaces.

Open in GitHub Codespaces

Walk through these pages in order:

  1. Deployment overview: architecture and the external dependencies you need to provision.
  2. Kind deployment: spin up the whole stack on a kind cluster (on your machine or a DigitalOcean cloud VM) for evaluation, including an optional self-contained authentication setup with Dex (or an external OIDC provider).
  3. AWS deployment: a minimal values.yaml, the helm install command, object-storage access, ingress, and a worked AWS/EKS example — for flyte-binary or flyte-core.
  4. Authentication and SSO: securing the API and putting single sign-on in front of the console.
  5. Enable app serving: running long-running apps on Knative, including how to install the Knative Serving prerequisite.
  6. Plugin setup: cluster-side configuration some plugins need, including copilot's access to your object store.

{{< subpage-cards >}}