Production installation with Kubernetes


You can save time by using hosted Mender, a secure Mender Server ready to use, maintained by the Mender developers.

This section is a step by step tutorial for deploying the Mender Server for production environments, and will cover relevant security and reliability aspects of Mender production installations. Most of the steps are the same whether you are installing the Open Source or Enterprise edition of the Mender Server, but some extra are are highlighted for the latter.

You will use the Helm chart to deploy to production the Mender backend services on a Kubernetes cluster.

Please read the Requirements page to understand what combinations are validated by that is clear please move on the first paragraph Kubernetes.

Requirements and resources

The requirements listed below are what tests internally and supports for production installations of the mender server. Alternative providers might technically work as well, but are not officially supported.

Platform and software dependencies

Artifact storage:

  • Azure blob storage
  • S3 compatible:
    • AWS S3
    • Cloudflare R2
    • GCP - S3 compatible API only
    • Minio

Mongo DB: Mender supports MongoDB in both Standalone (single node) and Replica set mode. We recommend using a replica set for high availability production environments, and you can choose to host your own cluster or use the MongoDB Atlas managed service.

  • Supported versions:
    • MongoDB 5.0
    • MongoDB 4.4

Please note that we do not provide support for troubleshooting issues with MongoDB not directly related to the Mender product.


  • Redis 6.0, 6.2
    • ElasticCache (AWS)
    • AzureCache
    • Memorystore (GCP)
    • Self hosted


  • NATS 2.7, 2.8, 2.9

Whatever the supported Kubernetes version for:

Helm CLI version:

  • 3.7


To deploy a production-grade Mender Server, you will need Kubernetes worker nodes providing at least 4 GB of RAM, 4 vCPUs and 10 GB for the persistent volumes.

The Mender backend is available for the x86 architecture only.

We welcome contributions to improve this documentation. To submit a change, use the Edit link at the top of the page or email us at .