Hey, I just noticed there is a single binary deplo...
# flyte-deployment
h
Hey, I just noticed there is a single binary deployment available for Flyte. We are looking to migrate our current deployment to a new EKS cluster, and I was thinking of deploying it using a single binary as looks awesome! We are currently leveraging OAuth2 authentication, based on the docs. However, with the new binary I would imagine the auth setup to be simplified, but the docs for single cluster production-grade deployment yields a 404 in terms of authentication (https://docs.flyte.org/en/latest/deployment/deployment/cloud_production.html#authentication). I would assume the app for flytepropeller is obsolete for binary deployments as there is no need for authenticated requests between the flyte components? Is there an updated guide that we can use?
s
The link's broken. We'll need to fix it. Please refer to https://docs.flyte.org/en/latest/deployment/configuration/auth_setup.html page. cc @Niels Bantilan
h
We use that currently, but I was assuming that flytepropeller app is not needed since we use a single binary?
s
Not very sure. @Yee could you clarify please?
y
No you still need it unfortunately.
Even though it’s a single binary they’re still different pieces of code.
And they talk over the local host network
h
Understood, thanks!
y
Of course
n
FYI just set up a redirect to the 404'ing page, it should go to the new page
122 Views