SiteWhere / Kubernetes integration including Helm Charts

This chart will do the following:

• Deploy SiteWhere Infrastructure:

  • Deploy MongoDB
  • Deploy Apache Kafka
  • Deploy Apache Zookeeper
  • Deploy Apache Syncope
  • Deploy Prometheus
  • Deploy Eclipse Mosquitto

• Deploy SiteWhere Microservices. The table bellow describes the microservices deployed base on the profile selected.

  Microservice	Defaul Profile	Minimal Profile
  Asset Management	✓	✓
  Device Management	✓	✓
  Event Management	✓	✓
  Event Sources	✓	✓
  Inbound Processing	✓	✓
  Instance Management	✓	✓
  Outbound Connectors	✓	✓
  Web Rest	✓	✓
  Batch Operations	✓	✗
  Command Delivery	✓	✗
  Device Registration	✓	✗
  Device State	✓	✗
  Event Search	✓	✗
  Label Generation	✓	✗
  Rule Processing	✓	✗
  Schedule Management	✓	✗
  Streaming Media	✓	✗

• Expose Web Rest port 80 on an external Istio Ingress.

• Expose MQTT port 1886 on an external LoadBalancer.

To install SiteWhere Helm Chart follow this instructions.

The following tables list the configurable parameters of the SiteWhere chart and their default values.

Each microservice has the following configuration:

If you install SiteWhere in debug mode (using --set services.debug=true) each microservice will expose two port (JDWP Port and JMX Port) for remote debuging. The following table show the port that each microservice will expose, so that you can connect a remote debuger.

In order to deploy SiteWhere using an external infrastructure of Kafka and Zookeeper, install SiteWhere setting sitewhere-infra-core.enabled=false. Also you need to provide the location of Apache Zookeeper (hostname and port) and Apache Kafka Bootstrap servers location (hostname and port).

helm install --name sitewhere \
  --set sitewhere-infra-core.enabled=false \
  --set sitewhere-infra-core.zookeeper_host=<zk-locahost> \
  --set sitewhere-infra-core.zookeeper_port=<zk-port> \
  --set sitewhere-infra-core.kafka_host=<kafka-locahost> \
  --set sitewhere-infra-core.kafka_port=<kafka-port> \
  sitewhere/sitewhere