It seems likely that you can use an external authorization server for HTTPS while using the internal self-auth server for internal communications. According to the
Flyte documentation, Flyte supports both internal and external authorization servers. The internal server is suitable for quick start and testing, while the external server is recommended for more control over security settings.
Regarding internal communication, such as between FlyteAdmin and FlytePropeller, it seems likely that this happens via gRPC. The
Flyte documentation mentions that Flyte components interact with each other as part of its authentication implementation, which typically involves gRPC for communication.
Would you like more detail on any specific part of this setup?
Sources:
-
Flyte documentation 👍 0 button 👎 0 button 💡
Hint: Mention @runllm in the thread for followups.