Hi, i m trying to deploy flyte-core on an AKS cluster that uses nginx-ingress-controller and to handle grpc routing I used

separateGrpcIngress: true

, so nginx controller can handle http and http2. However using same fqdn does not make nginx-ingress-controller happy really.. I m getting

Warning  Rejected  8m28s  nginx-ingress-controller  All hosts are taken by other resources

error on one of the ingress objects (depending on which one is applied first, it changes.) Apparently nginx does not support multiple ingress objects for the same host/fqdn. When I try to deploy with only one ingress object, then grpc protocol is not supported. So, I was wondering if anyone made it work with some kind of magical configuration. PS: I tried

mergeable-ingress-types

as well, but no luck :(

@hfurkanvural I still need to test this with flyte-core but take a look at these annotations: https://github.com/flyteorg/flyte/blob/243a8cb3e38b09307c40bc24b206f408a1192d9f/charts/flyte-core/values-gcp.yaml#L151-L164 (except for the one about

cert-manager

)

@David Espejo (he/him) Thanks, i tried with that config and unfortunately it s still the same 😞 I guess nginx-ingress is not an option in this case