Mutual TLS and Load Balancing
Control who is allowed to join your hub, and spread a stream across several outputs instead of one. This release also makes sure every node ends up running the network you configured, whether or not it was online when you made the change.
Mutual TLS between nodes and hub servers
A node can now prove who it is with a certificate you issued, and a hub can be set to accept only nodes that carry one. Anything without a valid certificate is turned away, so joining a hub is no longer just a matter of knowing the address.
Distribute packets across outputs
The new load balancer component splits a stream across several outputs, and you decide how much each one carries. Send most of a feed down your primary path and keep a smaller share on a backup, or spread it evenly across three links. Pipelines can also start dropping packets once their buffer grows past a limit you set, so a congested pipeline sheds load instead of piling up delay.
Improvements
- KPIs / A KPI value that cannot be worked out now shows a dash with the reason in a tooltip, instead of an error.
- Telemetry / You can now choose how often telemetry is collected.
Fixes
- Networks / Nodes follow their network more closely. Deleting a network, or removing a node from the hub, no longer leaves pipelines running behind, even when the node was offline at the time, and a node that has no instance yet gets one when the network updates.
- Pipelines / Pipelines deployed as part of a network now report their real state in the UI and the CLI, stop when deleted, toggle the right way, and no longer get stuck waiting to restart.
- Blueprints / A blueprint that fails to compile no longer takes the network's other running pipelines down with it, and a blueprint a network is built from can no longer be deleted out from under it.
- Streams / Event streams no longer miss changes made right after a stream is opened, and clients can wait for a subscription to be live before acting on it.
- Hub / Several crashes during startup and shutdown are fixed, and a request made right after a node connects no longer fails for no reason.