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 following Requirements and resources section to understand what combinations are validated by Northern.tech.
The requirements listed below are what Northern.tech tests internally and supports for production installations of the mender server. Alternative providers might technically work as well, but are not officially supported.
Here are the hardware requirements for the Mender Server (excluding the database and artifact storage requirements):
Currently, the MongoDB setup included in the Helm Chart only supports x86_64 architecture. If you want to use arm64, you will need to set up an external MongoDB cluster.
Artifact storage:
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.
Please note that we do not provide support for troubleshooting issues with MongoDB not directly related to the Mender product.
Redis:
Nats:
Whatever the supported Kubernetes version for:
Helm CLI version:
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 and arm64 architecture only.
© 2024 Northern.tech AS