# Installing on Kubernetes **URL:** https://meta.discourse.org/t/installing-on-kubernetes/49329 **Category:** Self-hosting **Tags:** unsupported-install **Created:** [August 27, 2016, 10:59pm UTC](https://meta.discourse.org/t/installing-on-kubernetes/49329 "2016-08-27T22:59:09Z") **Posts on this page:** 1 **Showing post:** 37
### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking) #### Post date: [February 9, 2020, 9:38pm UTC](https://meta.discourse.org/t/installing-on-kubernetes/49329/37 "2020-02-09T21:38:40Z")
You may be interested in a multi site configuration. > [@Multisite configuration with Docker](https://meta.discourse.org/t/multisite-configuration-with-docker/14084): > > warning While multisite is supported in the Discourse application, this is an advanced sysadmin setup. If you don’t know what you’re doing, do not set up multisite. The Discourse team is unable to provide multisite configuration support. If you wish to host multiple domains on a singled Docker setup, you’ll need a multisite configuration. Here are the basic building blocks for one. Understand hooks Multisite is a fairly advanced topic. Before attempting a multisite build, spend some time… There’s two big problems you’re running into: Discourse isn’t ready for Kubernetes, so custom code is required. And you’re edging into what the Discourse team does to make money (hosting a large number of forums), so the level of support you’re getting will drop off. My advice? Do a multisite configuration with static scheduling onto VMs, entirely outside your cluster. (Or a Service Type=ExternalName pointing to the VM to keep the same Ingress.) --- _[View the full topic](https://meta.discourse.org/t/installing-on-kubernetes/49329)._