# Discource in Kubernetes (K8S)

**URL:** https://meta.discourse.org/t/discource-in-kubernetes-k8s/164202
**Category:** Self-hosting
**Tags:** unsupported-install
**Created:** [September 16, 2020, 12:36pm UTC](https://meta.discourse.org/t/discource-in-kubernetes-k8s/164202 "2020-09-16T12:36:59Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Nikolay\_Bogdanov](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nikolay_bogdanov/32/193924_2.png) [@Nikolay\_Bogdanov](https://meta.discourse.org/u/Nikolay_Bogdanov)
#### Post date: [September 16, 2020, 12:36pm UTC](https://meta.discourse.org/t/discource-in-kubernetes-k8s/164202/1 "2020-09-16T12:36:59Z")

</div>

Hello. My company is trying to setup the Discourse in our infrastructure for the user content. So I created the image with Ruby code and Helm chart. I deployed the application to k8s without any problem. But our content manager got problems with the admin page - it showed an old value for changed field. I checked the database - everything was good. I saw a new value in the **site\_settings** table. So I decided to investigate how server was started. I found that the puma app server was started with 4 workers. I decreased a workers to 1 and problem was solved.  
So my question is: how should I fix this for clustering setup? Does shared setting cache exist for the Discourse?