Summary
The user is experiencing difficulties registering workflows to a cloud-hosted cluster and suspects a configuration error. They reference a past issue that was resolved by adding a gRPC annotation to the nginx ingress, which enabled the ingress controller to accept HTTP2 requests. The user mentions adding the annotation nginx.ingress.kubernetes.io/backend-protocol: "GRPC" to the ingress ending with "-grpc".
rahulmadanraju
Thanks, <@U07S21J8W9L>. Seems like the following configuration is already set. Strange but also weird that on redeploying the image with a different tag resolved the issue.
jeremy221
I use nginx ingress so I add this annotation <http://nginx.ingress.kubernetes.io/backend-protocol|nginx.ingress.kubernetes.io/backend-protocol>: "GRPC" to the ingress end with "-grpc"
rahulmadanraju
Yes, that's exactly how it is deployed. Could you please elaborate more on where the things were changed/adapted?
jeremy221
Did you deploy Flyte on K8s on Cloud? I met the same issue before. In my case, I did not add the gRPC annotation on the nginx ingress so the ingress controller refuses http2 requests. Hope this helps!
rahulmadanraju
Hey Flyte Community, I am trying to register my workflows to cluster hosted on Cloud. Unfortunately, I am not able to register my workflows anymore due to the following error. Could you let me know of a possible solution here? Am I missing something in my config.? Thanks!