How to make rasa-x accessible through a subpath (e.g /rasa) using our nginx ingress controller?

Rasa Open Source
1

Hello, we have installed rasa-x in our kubernetes cluster. However, it seems that it can only be accessible through a root path (/) if we disable the default nginx and use our nginx ingress controller. Is there any configuration to make it accessible through a subpath (e.g /rasa) ?

Here is our ingress resource that we used but it doesn’t work :

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: "rasa-x-ingress"
  namespace: "rasa"
  annotations:
    kubernetes.io/ingress.class: nginx
 spec:
   rules:
   - http:
     paths: 
      - path: /rasa
        backend:
          serviceName: rasa-rasa-x-rasa-x
          servicePort: 5002
2

Hi,

Configuration for Rasa X in a case where you wanna use nginx-ingress required more than your example.

The rasa-x helm chart has a ready configuration for nginx-ingress:

You can use it as a point start.

3

the helm chart exposes rasa-x on root path not on subpath

4

My point here was that it’s the example that you can take and try to modify in order to achieve what you want.

For example, you can try to use nginx.ingress.kubernetes.io/rewrite-target: /$2 annotation and a path: /rasa(/|$)(.*).

There is no ready configuration to use subpath for nginx-ingress.

Additionally, afaik Rasa X uses a root path for other components, for example, all static content or API requests use a root path and it might turn out it’s harder than it seems, to use a subpath.

1 Like
5

How can I expose all static content on subpath also?

6

Facing same problem. Why the path value is not configurable using values.yml file ? Even if I update host path in ingress service, it is creating elb for the root path