# Setting Rasa X to Production Ready in K3S containers

**URL:** <https://forum.rasa.com/t/setting-rasa-x-to-production-ready-in-k3s-containers/30049>\
**Category:** \[Deprecated\] Rasa X Community Edition\
**Created:** [June 10, 2020, 2:02pm UTC](https://forum.rasa.com/t/setting-rasa-x-to-production-ready-in-k3s-containers/30049 "2020-06-10T14:02:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![depicus](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/depicus/32/9539_2.png) [@depicus](https://forum.rasa.com/u/depicus)\
**Post date:** [June 10, 2020, 2:02pm UTC](https://forum.rasa.com/t/setting-rasa-x-to-production-ready-in-k3s-containers/30049/1 "2020-06-10T14:02:59Z")

</div>

I’ve used the one stop install script to install Rasa and Rasa X using Multipass on my Mac. So far so good, I had a previous model with some training and managed to get it on Github and into Rasa X and I’ve had somebody else try it from the links but I’m struggling to make it production ready. There isn’t a _credential.yml_ file in the Rasa X interface so I’ve used the one created with `rasa init` and amended the _credential.yml_ then pushed to Github but after rebooting the k3s server I still cannot get **socketio** to work.

So what is the correct way to amend the _credential.yml_ file on a k3s cluster to make the service production ready ?

Thanks.

---

<div class="post-metadata">

**Author:** ![erohmensing](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/erohmensing/32/1789_2.png) [@erohmensing](https://forum.rasa.com/u/erohmensing)\
**Post date:** [June 11, 2020, 11:44am UTC](https://forum.rasa.com/t/setting-rasa-x-to-production-ready-in-k3s-containers/30049/2 "2020-06-11T11:44:36Z")

</div>

Hey @depicus, the credentials don’t come in from Git – there’s instructions on each of the deployment pages about how to set up external channels. For the k3s deployment the instructions can be found here: [One-Line Deploy Script](https://rasa.com/docs/rasa-x/installation-and-setup/one-line-deploy-script/#applying-the-settings)

Basically you export the credentials to an `ADDITIONAL_CHANNEL_CREDENTIALS` environment variable and then re-run the deployment with the `-E` flag to apply it.
