Enabling OSM is blocking the upload of documents received as a payload string content

[manojbale]

We have a GRAPHQL backend service (deployed in Azure Kubernetes services) with the OSM add-on enabled and being used as backend for our mobile applications.

We have configured ingress backends and egress policies for our graphql backend service. Every functionality of our mobile application works fine when OSM is enabled.

However the documents upload functionality in the mobile applications is timing out when OSM is enabled.

But there are no issues observed with document upload if OSM is disabled (namespace removed from OSM) for the application.

We are not sure what is causing the issue. Is there any limitation with OSM for allowing a file content as string type content in the request body to graphql? We are not seeing errors in the OSM controller log, but we see the following error message in the ingress controller pod.

[error] 106#106: *74780367 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 10.85.32.213, server: , request: "POST /bff-test/graphql HTTP/1.1", upstream: "http://10.85.32.88:4000/graphql", host: ""

We are using NGINX ingress controller. Below are the configurations

-------INGRESS--------- apiVersion: v1 items:

• apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: kubernetes.io/ingress.class: nginx meta.helm.sh/release-name: appname meta.helm.sh/release-namespace: appnamespace nginx.ingress.kubernetes.io/force-ssl-redirect: "true" nginx.ingress.kubernetes.io/proxy-body-size: 20m nginx.ingress.kubernetes.io/rewrite-target: /$1 nginx.ingress.kubernetes.io/ssl-redirect: "true" creationTimestamp: "2022-12-30T08:39:59Z" generation: 1 labels: app: appname app.kubernetes.io/managed-by: Helm name: appname namespace: appnamespace spec: rules:

  • host: app_fqdn http: paths:
    • backend: service: name: appname port: number: 443 path: /bff-test/metrics pathType: ImplementationSpecific
    • backend: service: name: appname port: number: 443 path: /bff-test/?(.*) pathType: ImplementationSpecific tls:
  • hosts:
    • app_fqdn secretName: app_secret status: loadBalancer: ingress:
    • ip: public_ip_address of public AKS load balancer kind: List metadata: resourceVersion: ""

  --------INGRESSBACKEND-----------

  apiVersion: v1 items:

• apiVersion: policy.openservicemesh.io/v1alpha1 kind: IngressBackend metadata: annotations: meta.helm.sh/release-name: appname meta.helm.sh/release-namespace: appnamespace generation: 2 labels: app.kubernetes.io/managed-by: Helm name: appname namespace: appnamespace spec: backends:
  • name: appname port: number: 4000 (target port of our service) protocol: http sources:
  • kind: Service name: nginx-ingress-nginx-controller-internal (private IP address of private Load balancer) namespace: ingress-nginx status: currentStatus: committed reason: successfully committed by the system kind: List metadata: resourceVersion: ""