Hey so i deployed my rasax chatbot on kubernetes. The way i connected my chatbot locally with external analytics was to put an event broker in the endpoints.yml file and installing dashbot in the pip environment. How do i do the same for the kubernetes deployment? Its likely to do in the values.yml file right? event_broker: type: dashbot.rasa.rasa apiKey: “PLACEHOLDER” let me know in what way to do it thanks

Sorry for the confusion but I wasn’t suggesting you replace rabbit with kafka. The example was intended to show how you can configure a different event broker. In your case, you need to replace rabbit with the dashbot broker. Rasa doesn’t not support multple event brokers. Based on your config, you are using the rabbit broker to send events to Rasa X. You could replace rabbit with the dashbot config but your Rasa X instance will no longer receive the conversations. Rabbit does allow you to create multiple queues, so it’s possible you could create a second queue that would be forwarded to Dashbot but then you would need to re-write the dashbot.rasa.rasa code to read from the rabbit queue directly. Otherwise you could disconnect Rasa X and just use Dashbot.

# Default values for rasa-x. # This is a YAML-formatted file. # Declare variables to be passed into your templates. # rasax specific settings rasax: # override the default command to run in the container command: [] # override the default arguments to run in the container args: [] # name of the Rasa X image to use name: "rasa/rasa-x" # gcr.io/rasa-platform/rasa-x-ee # tag refers to the Rasa X image tag (uses `appVersion` by default) tag: "" # port on which Rasa X runs port: 5002 # scheme by which Rasa X is accessible scheme: http # passwordSalt Rasa X uses to salt the user passwords passwordSalt: "passwordSalt" # token Rasa X accepts as authentication token from other Rasa services token: "rasaXToken" # jwtSecret which is used to sign the jwtTokens of the users jwtSecret: "jwtSecret" # databaseName Rasa X uses to store data # (uses the value of global.postgresql.postgresqlDatabase by default) databaseName: "" # disableTelemetry permanently disables telemetry disableTelemetry: false # Jaeger Sidecar jaegerSidecar: "false" # initialUser is the user which is created upon the initial start of Rasa X initialUser: # username specifies a name of this user username: "me" # password for this user (leave it empty to skip the user creation) password: "$CrvMe3i&ye3FdfvJR$t4KJ2" ## Enable persistence using Persistent Volume Claims ## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/ ## persistence: # access Modes of the pvc accessModes: - ReadWriteOnce # size of the Rasa X volume claim size: 10Gi # annotations for the Rasa X pvc annotations: {} # finalizers for the pvc finalizers: - kubernetes.io/pvc-protection # existingClaim which should be used instead of a new one existingClaim: "" # livenessProbe checks whether rasa x needs to be restarted livenessProbe: enabled: true # initialProbeDelay for the `livenessProbe` initialProbeDelay: 10 # scheme to be used by the `livenessProbe` scheme: "HTTP" # readinessProbe checks whether rasa x can receive traffic readinessProbe: enabled: true # initialProbeDelay for the `readinessProbe` initialProbeDelay: 10 # scheme to be used by the `readinessProbe` scheme: "HTTP" # resources which Rasa X is required / allowed to use resources: {} # extraEnvs are environment variables which can be added to the Rasa X deployment extraEnvs: [] # - name: SOME_CUSTOM_ENV_VAR # value: "custom value" # additional volumeMounts to the main container extraVolumeMounts: [] # - name: tmpdir # mountPath: /var/lib/mypath # additional volumes to the pod extraVolumes: [] # - name: tmpdir # emptyDir: {} # tolerations can be used to control the pod to node assignment # https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/ tolerations: [] # - key: "nvidia.com/gpu" # operator: "Exists" # nodeSele…

Thanks for the values.yml file. It looks like there’s an open issue here and workaround here

will try it out in a bit , fingers crossed. Absolutely appreciate you helping out, you have no idea how much this means to me.

im quite sure dashbot uses rabbitmq , so would i have to disable kafka?

Stephens the workaround doesn’t really work, disabling rabbitmq causes the following pods to crash [image] C:\Users\ayman\OneDrive\Bureaublad\VisualQuran\iChoosr-Rasa-chatbot>kubectl -n rasax logs rasa-x-1638803505-rasa-production-b7784bfd8-n89vr ←(0lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk←(B ←(0x←(B Rasa Open Source reports anonymous usage telemetry to help improve the product ←(0x←(B ←(0x←(B for all its users. ←(0x←(B ←(0x←(B ←(0x←(B ←(0x←(B If you'd like to opt-out, you can use `rasa telemetry disable`. ←(0x←(B ←(0x←(B To learn more, check out https://rasa.com/docs/rasa/telemetry/telemetry. ←(0x←(B ←(0mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj←(B ←[92mStarting Rasa X in production mode... 🚀←[0m Traceback (most recent call last): File "/opt/venv/bin/rasa", line 8, in <module> sys.exit(main()) File "/opt/venv/lib/python3.8/site-packages/rasa/__main__.py", line 121, in main cmdline_arguments.func(cmdline_arguments) File "/opt/venv/lib/python3.8/site-packages/rasa/cli/x.py", line 355, in rasa_x run_in_production(args) File "/opt/venv/lib/python3.8/site-packages/rasa/cli/x.py", line 414, in run_in_production _rasa_service(args, endpoints, None, credentials_path) File "/opt/venv/lib/python3.8/site-packages/rasa/cli/x.py", line 89, in _rasa_service serve_application( File "/opt/venv/lib/python3.8/site-packages/rasa/core/run.py", line 178, in serve_application app = configure_app( File "/opt/venv/lib/python3.8/site-packages/rasa/core/run.py", line 103, in configure_app app = server.create_app( File "/opt/venv/lib/python3.8/site-packages/rasa/server.py", line 650, in create_app Initialize( File "/opt/venv/lib/python3.8/site-packages/sanic_jwt/initialization.py", line 133, in __init__ self.__load_configuration() File "/opt/venv/lib/python3.8/site-packages/sanic_jwt/initialization.py", line 306, in __load_configuration self.config = self.configuration_class(self.app.config, **self.kwargs) File "/opt/venv/lib/python3.8/site-packages/sanic_jwt/configuration.py", line 283, in __init__ self._validate_secret() File "/opt/venv/lib/python3.8/site-packages/sanic_jwt/configuration.py", line 308, in _validate_secret if self.secret() is None or ( File "/opt/venv/lib/python3.8/site-packages/sanic_jwt/configuration.py", line 134, in __call__ if asyncio.get_event_loop().is_running(): File "/usr/lib/python3.8/asyncio/events.py", line 639, in get_event_loop raise RuntimeError('There is no current event loop in thread %r.' RuntimeError: There is no current event loop in thread 'MainThread'. The production pod gives the following error

Hope you can help me out. Thank you

How come this does work locally though, rasaX and dashbot

Also disconnecting Rasa X and using dashbot only is not an option as they serve two different purposes.

What’s your endpoints.yml file look like when running locally?

Rasa & Dashbot & Kubernetes

[Deprecated] Rasa X Community Edition

aymane258 (Aymane258) December 14, 2021, 6:55pm 52

. @stephens

Topic		Replies	Views
How to install pip module into production pod in a kubernetes deployment [Deprecated] Rasa X Community Edition	2	2986	December 6, 2021
Rasa deployement via helm Rasa Open Source	7	1017	August 31, 2022
Rasa run --enable api equivalent in RasaX kubernetes deployment? [Deprecated] Rasa X Community Edition	4	808	December 3, 2021
Open Source Deployment On Kubernetes Deploys Rasa-X Rasa Open Source	6	1240	August 17, 2023
I cannot seem to get rasax and rasa deployed seperately and connected together [Deprecated] Rasa X Community Edition	10	1005	December 25, 2021

Rasa & Dashbot & Kubernetes

Related topics