If the life-cycle of your EWC services is handled by a third party orchestrator such as
Kubernetes, you will likely need to manually create sensor node assignments (single sensor
running inside a single sensor container) for all the running / configured sensors.
For more information, please refer to the st2sensorcontainer single sensor mode.

It may be desirable to partition sensors across multiple sensor nodes, either for load management
or security purposes. EWC offers several ways of doing this.

In this scheme the partition map is stored in the key-value store under a special sensor
node name scoped key. This is a way to provide a fixed map and does not help with any
dynamic mapping of sensors to sensor nodes.

This is a dynamic scheme where each sensor node is assigned one or more hash ranges. Each sensor itself
is hashed. and depending on which bucket of the range it fits into a sensornode runs the sensor. Hash
schema is particulaly useful when there are many sensors and relatively few nodes.

The special keys MIN and MAX can also be used. This is how a typical hash provider configuration
would look: