Karpor behind ingress getting error recv() failed (104: Connection reset by peer) while reading upstream

[vickydev90]

Hi,

I am trying to run karpor ui behind ingress but on hitting endpoint i get error "104: Connection reset by peer)".
Has anyone tried running karpor behind ingress?

here is my configuration

Karpor version - v0.6.1

ingress config -

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/proxy-buffer-size: 64k
    nginx.ingress.kubernetes.io/proxy-connect-timeout: 600s
    nginx.ingress.kubernetes.io/proxy-read-timeout: 600s
    nginx.ingress.kubernetes.io/proxy-send-timeout: 600s
    nginx.ingress.kubernetes.io/server-snippet: keepalive_timeout 120s;
  name: karpor-ingress
  namespace: karpor
spec:
  rules:
  - host: karpor.xyz.net
    http:
      paths:
      - backend:
          service:
            name: karpor-server
            port:
              number: 7443
        path: /
        pathType: Prefix

i have tried proxy read annotation but didn't work for me.
Appreciate any leads.

[elliotxx]

@vickydev90 Thanks for the feedback! In fact, the karpor-server in Live Demo is running behind ingress, and I will try to reproduce your problem later.

[surbanski-nr]

@vickydev90 you might be missing this annotation

  annotations:
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"

[vickydev90]

@surbanski-nr that was the missing piece, post adding above annotation, ui started working , thank you for quick help.

@elliotxx just a suggestion if we can integrate ingress as a part of our helm so one can enable it using flag and doesn't have to explicitly create it.

[elliotxx]

@vickydev90 Sorry for the late reply, I think this is a good idea! I created an issue #808 to follow up on it