Open thomas-riccardi opened 4 years ago
cc @Benjiiim
@thomas-riccardi Have you tried splitting it up into multiple Ingress objects as a workaround?
@thomas-riccardi Did you try @StianOvrevage's suggestion ?
@StianOvrevage @akshaysngupta splitting into multiple Ingress is indeed the workaround, but it has some limitations:
Is your feature request related to a problem? Please describe. I have different k8s Services behind one k8s Ingress with different paths rules, each having different application-level behavior, notably sane request timeouts.
Currently the request timeout can onlyt be configured at the Ingress level (with the
appgw.ingress.kubernetes.io/request-timeout
annotation), it then applies to all the rules (behind the scene all Application Gateway Rules use the same unique HTTP setting resource if I understand correctly).Describe the solution you'd like I'd like to be able to define different HTTP settings per Ingress rule/path. More precisely:
(In GCP GKE, they have a
BackendConfig
CRD pointed to by an annotation on the Service: https://cloud.google.com/kubernetes-engine/docs/concepts/backendconfig)