Hello. Thanks to the Flyte team for their work on this framework.
Real quick, using Flyte-Binary as a helm chart onto AWS EKS.
Trying to set up OIDC and/or OAuth2 via Auth0 and have been messing around with some configs but have been unsuccessful getting the
/console
endpoint to query the browser for login with variations off of the following values.yaml config:
auth:
enabled: true
enableAuthServer: false
oidc:
baseUrl: https://{DOMAIN}.<http://auth0.com/.well-known/openid-configuration|auth0.com/.well-known/openid-configuration>
clientId: {CLIENT ID}
clientSecret: {CLIENT SECRET}
authorizedUris:
- https://{LOAD BALANCED ADDRESS}.com
- https://{LOAD BALANCED ADDRESS}.com
Bit unsure how to transpose the documentation from the official site into
flyte-binary
as the documentation seems to only go over
flyte-core
or
flyte
.
The documentation doesn't seem to really exist for flyte-binary and there's scant discussion surrounding the topic unfortunately.
I understand on some level that there are three components to the Flyte deployment but how does one access those configurations through the Helm chart within the
flyte-binary
deployment? Specifically, how are you supposed to affect the various OIDC/auth config values when the templates for binary don't seem to match the documentation?
Also, we wish to use Auth0 as our external authorization server and don't need the internal server, but there have been conflicting resources suggesting that internal still needs to be defined.
Any help in the matter would be most appreciated.