Configuration#
This section will cover how to configure your Flyte cluster for features like authentication, monitoring, and notifications.
Important
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:
clientId: <IDP_CLIENT_ID>
clientSecret: <IDP_CLIENT_SECRET>
internal:
clientSecret: <CC_PASSWD>
clientSecretHash: <HASHED_CC_PASSWD>
authorizedUris:
- https://flyte.company.com #change to your authorized URI
inline:
#This section automates the IAM Role annotation for the default KSA on each project namespace to enable IRSA
#Learn more: https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html
cluster_resources:
customData:
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. |