nyejon
April 27, 2022, 5:59am
3
Hey Johan,
Glad I’m not the only one struggling. Based upon what I’ve gone through to get this working, I don’t believe very many people have taken a Rasa bot to production in a good way.
Maybe if you have a blank Kubernetes cluster dedicated to Rasa, without any security practices the helm chart will work fine.
I nearly have everything working now. I can provide you some guidance once I have the final bit working, but for now you can have a look at the issues I’ve opened on Github to point you in the right direction.
Most of the issues lie with the Network Policies being broken. The Rasa X policies can work with the rasa-oss but you need to add a component label to the rasa pod that matches “rasa-production” and “rasa-worker” (I disabled worker, although this just seemed to break things more and haven’t gotten down to investigate it).
Everything was a pain to debug, took over a week of time and left a sour experience in the mouth.
You can see all the issues I opened on their Github repositories here:
For the Rasa chart:
opened 10:29AM - 14 Apr 22 UTC
Hi,
The helm chart doesn't seem to allow setting custom secrets for these val… ues outside of the values file like the Rasa X Helm chart allows.
It would also help to have the naming between the different charts aligned, as it is very confusing dealing with multiple names referring to the same thing, across the charts.
Thanks,
Jonathan
opened 06:33AM - 22 Apr 22 UTC
Hi,
The network policy for redis points to the postgres port:
https://gith… ub.com/RasaHQ/helm-charts/blob/c93efed700651f80e1e90e8b8b7a09793957f360/charts/rasa/templates/network-policy/rasa-bot-redis.yaml#L13-L25
Can you please fix this to use the redis port value from the values file.
opened 01:28PM - 22 Apr 22 UTC
Hi, if I specify a different name, like "rasa-production" the network policies n… o longer apply.
See:
https://github.com/RasaHQ/helm-charts/blob/2875622c467c89fbb2ac00202c395852ea237075/charts/rasa/templates/network-policy/rasa-bot-allow-egress-http-https.yaml#L9
It should be something like: {{ include "rasa-common.names.fullname" . }}
opened 02:56PM - 26 Apr 22 UTC
https://github.com/RasaHQ/helm-charts/blob/e7e72f4a3333cb42430c0f49d001cb7d03fda… f74/charts/rasa/templates/helpers/_duckling.tpl#L5
This results in the following:
if false or (true and (not true)) resulting in false. We need this to be true when external = true and external url = true.
{{- if or .Values.duckling.install (and .Values.duckling.external.enabled .Values.duckling.external.url) -}} would be better.
This means the duckling endpoint is not provided to the pod here:
https://github.com/RasaHQ/helm-charts/blob/e7e72f4a3333cb42430c0f49d001cb7d03fdaf74/charts/rasa/templates/_containers-env.yaml#L21-L23
For the Rasa-X chart:
opened 01:22PM - 26 Apr 22 UTC
Hi
Please add the ability to add pod annotations like the rasa chart here:
…
https://github.com/RasaHQ/helm-charts/blob/e7e72f4a3333cb42430c0f49d001cb7d03fdaf74/charts/rasa/values.yaml#L243
Thank you
opened 01:44PM - 22 Apr 22 UTC
https://github.com/RasaHQ/rasa-x-helm/blob/68b36820918c26074fe662491150e821baf64… d20/charts/rasa-x/templates/network-policy.yaml#L224
This should apply to all network policies. It is done in some places but really inconsistent.
See: https://github.com/RasaHQ/helm-charts/issues/75 for the related issue in the rasa helm chart.
opened 03:37PM - 20 Apr 22 UTC
Hi,
Can you please enable redis to use a custom secret name like rabbit?
`… ``
# -- Existing secret with RabbitMQ credentials (must contain a value for `rabbitmq-password` key)
existingPasswordSecret: ""
```
At the moment it is forced to use a secret with the name: rasa-x-redis
Thanks
opened 03:28PM - 19 Apr 22 UTC
```
return await await_and_return_response(args, kwargs, request)
File "… /usr/local/lib/python3.8/dist-packages/rasax/community/api/decorators.py", line 176, in await_and_return_response
response = await response
File "/usr/local/lib/python3.8/dist-packages/rasax/community/api/decorators.py", line 84, in decorated_function
return await f(request, user=user, *args, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/rasax/community/api/blueprints/models.py", line 69, in upload_model
minimum_version = await model_service.minimum_compatible_version()
File "/usr/local/lib/python3.8/dist-packages/rasax/community/services/model_service.py", line 208, in minimum_compatible_version
info = await stack_service.version()
AttributeError: 'NoneType' object has no attribute 'version'
INFO:sanic.access:
```