Skip to main content

Install flytectl

brew install flyteorg/homebrew-tap/flytectl
To upgrade an existing installation:
flytectl upgrade

Verify the installation

flytectl version
Your flytectl version should be >= 0.2.0.

Configure flytectl

flytectl reads its configuration from ~/.flyte/config.yaml by default. You can override this path with the --config flag or by setting the FLYTECTL_CONFIG environment variable.
export FLYTECTL_CONFIG=/path/to/custom/config.yaml
The config file is also searched in:
  • $HOME/.flyte/config.yaml (default)
  • Current working directory
  • /etc/flyte/config

Generate a config file

Use flytectl config init to write a starter config automatically:
1

For a local demo cluster

flytectl config init
This writes ~/.flyte/config.yaml pointing to localhost:30081.
2

For a remote cluster

flytectl config init --host flyte.myexample.com
3

For a remote cluster with insecure connection

flytectl config init --host flyte.myexample.com --insecure
4

Verify the config is valid

flytectl config validate

Config file format

admin:
  # gRPC endpoint — use dns:/// prefix for DNS-based load balancing
  endpoint: dns:///localhost:30081
  insecure: true          # Set to false to require TLS
  authType: Pkce          # Options: ClientSecret, Pkce, ExternalCommand
Automatically written by flytectl demo start or flytectl config init.
admin:
  endpoint: dns:///localhost:30081
  insecure: true
  authType: Pkce
admin:
  endpoint: dns:///flyte.myexample.com
  authType: Pkce
  insecure: false
admin:
  endpoint: dns:///flyte.myexample.com
  authType: Pkce
  insecure: false
admin:
  endpoint: dns:///flyte.myexample.com
  authType: Pkce
  insecure: false
storage:
  type: s3
  container: my-flyte-bucket
  connection:
    region: us-east-1
    auth-type: iam
For production deployments, set insecure: false and configure authType: Pkce or authType: ClientSecret.

Build docs developers (and LLMs) love