Summary
The user sought help with deploying the flyte-core Helm chart on Kubernetes using Kong as ingress, facing issues with workflow registration via flyteclt, which they believed were related to ingress configuration. They encountered a "too large http2 frame" error during registration, with similar errors in the ingress logs. After assistance, they resolved the issues, which included the lack of TLS configuration in Flyte and Kong's limitation of not allowing both https(s) and grpc(s) ports on a single service. As a workaround, they created a separate service since the Helm chart does not support this configuration. The user also mentioned considering opening a PR to add this to flyte-core and inquired why it was only added to flyte-binary.