coeaimrm
(Manas Ranjan Mohanty)
May 31, 2020, 5:47am
20
I face similar problem while deploying in docker container. Then i deployed in kubernetes and prior to that i also added the k3s config file in ./bashrc terminal as it asked…
KUBECONFIG=“~/.kube/config:/etc/rancher/k3s/k3s.yaml”
It almost fixed all problems…
I have followed this too.
https://rasa.com/docs/rasa-x/installation-and-setup/openshift-kubernetes/
Hey I succeeded to make it work ! everything is OK now.
Steps I took :
-after install, do not forget to put the extra line export KUBECONFIG=/etc/rancher/k3s/k3s.yaml in the .bashrc file of your user (important)
-I ran “sudo kubectl get pod --namespace rasa” to have the list of the pods
-there you can note the name of the pods and the status. In my case the 2 following pods had a status “crachloopback” : rasa-rasa-worker and rasa-rasa-production. (no more on this printscreen as it is done af…