This section will cover how to configure your Flyte cluster for features like authentication, monitoring, and notifications.


The configuration instructions in this section are for the flyte and flyte-core Helm charts, which is for the multi-cluster setup.

If you’re using the flyte-binary chart for the single cluster setup, instead of specifying configuration under a yaml file like cloud_events.yaml in Cloud Events, you’ll need to add the configuration settings under the inline section in the eks-production.yaml file:

      - production:
        - defaultIamRole:
            value: <FLYTE_USER_IAM_ARN>
      - staging:
        - defaultIamRole:
            value: <FLYTE_USER_IAM_ARN>
      - development:
        - defaultIamRole:
            value: <FLYTE_USER_IAM_ARN>

Basic OIDC and Authentication Setup

Migration guide to move to Admin’s own authorization server.

Migration guide to move to Admin’s own authorization server.

Use Flyte’s cluster-resource-controller to control specific Kubernetes resources and administer project/domain-specific CPU/GPU/memory resource quotas.

Create new default configurations or overriding certain values for specific combinations of user projects, domains and workflows through Flyte APIs.

Guide to setting up and configuring notifications.

How to set up Flyte to emit events to third-parties.

Guide to setting up and configuring observability.

Improve the performance of the core Flyte engine.

Configure Flyte to to send events to external pub/sub systems.