# Installing on Kubernetes

**URL:** <https://meta.discourse.org/t/installing-on-kubernetes/49329>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [2016 年 8 月 27 日午後 10:59 UTC](https://meta.discourse.org/t/installing-on-kubernetes/49329 "2016-08-27T22:59:09Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![felicity](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/felicity/32/121572_2.png) [@felicity](https://meta.discourse.org/u/felicity)\
**Post date:** [2016 年 8 月 27 日午後 10:59 UTC](https://meta.discourse.org/t/installing-on-kubernetes/49329/1 "2016-08-27T22:59:09Z")

</div>

I’d like to install Discourse on our Kubernetes cluster. Kubernetes does not use the `docker` command to deploy images, so I’d need to build a Discourse image locally, push it to our private Docker registry, and then have Kubernetes pull the image from there. This is how we deploy other Docker-based software.

Can I do this by using `./launcher bootstrap` locally, then pushing the built image to our registry? Are there likely to be any problems from this approach? How would upgrading work in this case? (Kubernetes container instances can be destroyed at any time, so to upgrade, we’d want to build a new image and re-deploy, which Kubernetes lets us do without downtime.)

I understand I’ll need to provide settings for database (via environment variables), volume mounts for storage, etc. We plan to use our existing redundant Redis, PostgreSQL and GlusterFS services for this, like we do with other Docker applications.

---

_[View the full topic](https://meta.discourse.org/t/installing-on-kubernetes/49329)._