Path Prefix challenge with NR in Kubernetes

General
1

Hi all!

I have a challenge with Node Red in my Kubernetes Cluster.
The installation was done NodeRed und the Nginx-ingress via a HELM chart.
Good news are:
NR is available on

  • FQDN: http:// my.server.name:31827
  • IP: http:// 10.x.x.x:31827

I created an Ingress

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: nr-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
spec:
  tls:
  - secretName: tls-secret1
    hosts:
    - my.server.name
  rules:
  - host: my.server.name
    http:
      paths:
      - path: /nr
        backend:
          serviceName: my-nodered-node-red
          servicePort: 1880

When i do a Get http:// my.server.name/nr i see only parts working, see the screenshot:

On a single server i would normally setup an reverse proxy, specifying a root path prefix.
But how can i achieve that with a Kubernetes? Any ideas or solutions ?

ps: I posted this question also on Stackoverflow