Setting up connect docker image on kubernetes sending data to channel generates HTTP 404

[IQHT-DGH]

This is our first attempt at using the connect docker image on kubernetes and have hit an issue where connect is returning 404 when trying to send data to a channel.

The error seen is... [error] 1530#1530: *28276600 connect() failed (111: Connection refused) while connecting to upstream, client: 90.200.224.195, server: nextgen-connect-dev.mydomain.com, request: "GET /UpdateExternalPrimaryIdentifier HTTP/2.0", upstream: "http://10.105.0.75:22223/", host: "nextgen-connect-dev.mydomain.com"

The http url connect is using is nextgen-connect-dev.mydomain.com, my feeling is that this is the problem that is causing the 404 as that url essentially terminates at the NGINX controller and the message is passed to the connect pod/container using DNS and so is using http://Pod-IP-address:22223 and so really the http url should be localhost?

I've included the manifest files in use below, so that hopefully someone can spot a glaring error I've missed and the problem will do away.

Thanks in advance for any help resolving this.

Deployment manifest `apiVersion: apps/v1 kind: Deployment metadata: labels: service: mirth-connect name: mirth-connect spec: replicas: 1 selector: matchLabels: service: mirth-connect strategy: {} template: metadata: labels: service: mirth-connect spec: containers:

• image: docker.io/nextgenhealthcare/connect imagePullPolicy: IfNotPresent name: mirth-connect ports:
  • containerPort: 8443
  • containerPort: 22225
  • containerPort: 22223 env:
    • name: DATABASE value: sqlserver
    • name: DATABASE_URL value: dbconnection
    • name: DATABASE_USERNAME value: user
    • name: DATABASE_PASSWORD value: pass resources: limits: cpu: 150m memory: 350Mi requests: cpu: 100m memory: 250Mi restartPolicy: Always status: {} service manifest apiVersion: v1 kind: Service metadata: labels: service: mirth-connect name: mirth-connect namespace: development spec: type: ClusterIP ports:
      • name: "adminui" protocol: TCP port: 8083 targetPort: 8443
      • name: "pathology" protocol: TCP port: 22225
      • name: "primaryid" protocol: TCP port: 22223 selector: service: mirth-connect status: loadBalancer: {} SSL ingress manifest apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ingress-mirth-connect annotations: nginx.ingress.kubernetes.io/rewrite-target: / nginx.ingress.kubernetes.io/backend-protocol: "HTTPS" spec: ingressClassName: nginx tls:
      • hosts:
• "nextgen-connect-dev.mydomain.com" secretName: ingress-cert-secret rules:
  • host: "nextgen-connect-dev.mydomain.com" http: paths:
    • pathType: Prefix path: "/" backend: service: name: mirth-connect port: number: 8083 Channels ingress manifest apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ingress-mirth-connect-channels annotations: nginx.ingress.kubernetes.io/rewrite-target: / spec: ingressClassName: nginx tls:
  • hosts:
• "nextgen-connect-dev.mydomain.com" secretName: ingress-cert-secret rules:
  • host: "nextgen-connect-dev.mydomain.com" http: paths:
    • path: /UpdateExternalPrimaryIdentifier pathType: Prefix backend: service: name: mirth-connect port: number: 22223
    • path: /SavePathologyResults pathType: Prefix backend: service: name: mirth-connect port: number: 22225 `