Pages in Deployment
All the Eclipse Hono™ components can be deployed on Kubernetes, thanks to the resources YAML files that are provided through the repository. These files describe such components in terms of deployments and services in order to have the right pods running in the Kubernetes cluster so that they are able to communicate with each other.
OpenShift with EnMasse
This guide describes how to deploy Eclipse Hono™ using EnMasse as messaging backend on a single-master/single-node local OpenShift installation using “minishift”.
OpenShift with source-to-image (S2I)
This guide described how Eclipse Hono™ can be deployed on OpenShift with EnMasse using the source-to-image (S2I) way. Using this approach it is possible to customize and refresh the base images where Hono runs in. It also uses a more complex, multi-project setup and separates EnMasse and Grafana from the core Hono project.
Eclipse Hono™ components are distributed by means of Docker images which can be deployed to arbitrary environments where Docker is available. This section provides step-by-step instructions for deploying Hono to a cluster of Docker Engine nodes running in Swarm mode.
Limiting Resource Usage
Deploying Eclipse Hono™ to a container orchestration platform is easy thanks to the provided Docker images. This page provides some guidance for configuring the resource consumption of these containers in order to make sure that they get enough memory and CPU to run properly, but to also make sure that individual containers do not use up all the resources causing other containers to starve.