New RunLLM response generated: >>>*# Question* Hi, did anybody deployed flyte-core Helm chart on k8s using Kong as ingress? It seems that I have hit exactly this issue: https://kennethjenkins.net/posts/go-nginx-grpc/, it manifests when I'm trying top register a workflow using

flyteclt

. I wonder if there is a solution applicable on the ingress configuration side. # Answer The issue you're encountering with Kong as an ingress controller for Flyte is likely related to gRPC support, which can be tricky with some ingress controllers. According to this GitHub issue, gRPC requires HTTP/2, and not all ingress controllers support HTTP/2 for backend services. To resolve this, you need to ensure that HTTP/2 is enabled in your Kong configuration. You can refer to the Kong documentation for specific instructions on enabling HTTP/2. Would you like more detailed steps on configuring Kong for gRPC support with Flyte? Sources: - Flyte GitHub Issue #4962 - Kong documentation Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1723122764.485529 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.