# Path Prefix challenge with NR in Kubernetes

**URL:** <https://discourse.nodered.org/t/path-prefix-challenge-with-nr-in-kubernetes/11590>\
**Category:** General\
**Created:** [27 May 2019 10:27 UTC](https://discourse.nodered.org/t/path-prefix-challenge-with-nr-in-kubernetes/11590 "2019-05-27T10:27:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mchoeti](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@mchoeti](https://discourse.nodered.org/u/mchoeti)\
**Post date:** [27 May 2019 10:27 UTC](https://discourse.nodered.org/t/path-prefix-challenge-with-nr-in-kubernetes/11590/1 "2019-05-27T10:27:10Z")

</div>

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

```auto
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](https://stackoverflow.com/questions/56293915/kubernetes-ingress-needs-reverse-proxy-setting)