#3823 [Core feature] Support more gRPC configuration in agent-service plugin Issue created by honnix Motivation: Why do you think this is important? Currently

agent-service

plugin has hardcoded gRPC opts e.g.

insecure

. For use cases talking to a gRPC service that Flyte operator has no control of, the default hardcoded opts may not be sufficient or may not even work. Goal: What should the final outcome look like, ideally?

agent-service

can be configured to support extended gRPC configuration. Describe alternatives you've considered Forcing the gRPC service to be compliant with

agent-service

, but this may not always be achievable. Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte