square-agency-59624
09/24/2025, 9:57 PMancient-wolf-19325
09/24/2025, 9:57 PMauthType: ClientSecret, set the authType to ClientSecret in your client config (e.g., flytectl or flytekit), and provide the clientId and clientSecretLocation (path to the secret file). Ensure the corresponding confidential client and secret are registered in your IdP and Flyte deployment. Example config:
admin:
endpoint: dns:///flyte.example.com
authType: ClientSecret
clientId: flytepropeller
clientSecretLocation: /etc/secrets/client_secret
scopes:
- all
Make sure the secret file does not contain a trailing newline, and that the Flyte deployment's Helm values or Kubernetes secrets match the client credentials. For more, see flytekit/configuration/internal.py, flyte-core/values-keycloak-idp-flyteclients-without-browser.yaml, and issue #2849.
Would you like a step-by-step breakdown or details for a specific platform (e.g., AWS, GCP, Keycloak)?
Sources:
- flytekit/configuration/internal.py
- Issue #2849
- flyte-core/values-keycloak-idp-flyteclients-without-browser.yaml 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.square-agency-59624
09/24/2025, 10:14 PMancient-wolf-19325
09/24/2025, 10:14 PMauth.enabled, auth.oidc.baseUrl, auth.oidc.clientId, auth.oidc.clientSecret, and `auth.internal.clientId`/`clientSecret` are set appropriately. Use Kubernetes Secrets for sensitive values and reference them in the chart as needed.
You should also configure storage buckets, resource limits, and any required inline or external configuration overrides. For more, see the flyte-binary values.yaml and README.
Would you like a detailed checklist or example values file?
Sources:
- flyte-binary values.yaml
- flyte-binary README.md 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.