Architecture
A Flyte cluster is composed of the following core services:| Component | Role |
|---|---|
| FlyteAdmin | API server that accepts workflow registrations and execution requests over HTTP and gRPC |
| FlytePropeller | Kubernetes controller that drives workflow execution by reconciling FlyteWorkflow CRDs |
| FlyteConsole | React-based web UI for browsing workflows, executions, and artifacts |
| DataCatalog | Caching service that stores and retrieves task output metadata for memoization |
| FlyteScheduler | Native cron-style scheduler that triggers time-based workflow launches |
Deployment models
Local sandbox
Single Docker container running k3s, MinIO, and PostgreSQL. Ideal for development and testing. Start in one command with
flytectl demo start.Single binary
All Flyte services compiled into a single Go binary, deployed on Kubernetes using the
flyte-binary Helm chart. Best for teams that want a production-capable cluster without multi-service complexity.Full (flyte-core)
Each Flyte component runs as an independent Kubernetes Deployment. Use the
flyte-core Helm chart when you need fine-grained scaling, multi-cluster execution, or custom per-component configuration.Choosing a deployment model
I want to try Flyte locally
I want to try Flyte locally
Use the local sandbox. Run
flytectl demo start and you have a fully functional Flyte cluster in under two minutes. No Kubernetes knowledge required.I want a production cluster for a small team
I want a production cluster for a small team
Use the single binary (
flyte-binary Helm chart) deployed on EKS or GKE. It supports all plugins, authentication, and blob storage backends. It is simpler to operate than the full chart because all components share one pod.I need fine-grained scaling or multi-cluster execution
I need fine-grained scaling or multi-cluster execution
Use the flyte-core Helm chart. This deploys FlyteAdmin, FlytePropeller, DataCatalog, and FlyteConsole as separate Deployments, each with independent resource limits and replica counts. It is required for the multi-cluster execution model.
I'm deploying on-premises without cloud object storage
I'm deploying on-premises without cloud object storage
Use the single binary or flyte-core chart with MinIO as the object store. See the on-premises guide.
Platform guides
AWS (EKS)
Deploy on Amazon EKS with S3, RDS PostgreSQL, and IAM Roles for Service Accounts (IRSA).
GCP (GKE)
Deploy on Google Kubernetes Engine with GCS, Cloud SQL, and Workload Identity.
On-premises
Deploy on self-hosted Kubernetes with MinIO and a local PostgreSQL instance.
Single binary
Bootstrap Flyte on a single Kubernetes node using the
flyte-binary Helm chart.Configuration & security
Configuration overview
How config files, Helm values, and environment variables interact.
Authentication
OIDC/OAuth2 setup with Okta, Google, Azure AD, and Keycloak.
Storage
Configure S3, GCS, Azure Blob, and MinIO backends.
Secrets
Inject secrets into task pods from Kubernetes Secrets, AWS Secrets Manager, or Vault.
RBAC
Map OIDC claims to Flyte project and domain permissions.
Security overview
Non-root containers, network policies, TLS, and audit logging.
Plugin guides
Plugins overview
Enable backend plugins that extend Flyte’s task execution capabilities.
Spark
Run Apache Spark jobs on Kubernetes using spark-on-k8s-operator.
Ray
Run distributed Ray jobs using the KubeRay operator.
KFPyTorch
Run distributed PyTorch training with the Kubeflow training-operator.