Release 0.18.7
What's New
- Update ziti-tunnel service polling
- Now uses new api (when available) to skip refreshing services if no services have been changed
- Polling rate is passed through to sdk, so actual poll rate is now controlled
- Don't panic on router startup, just show error message and exit
- Fix resource leak: go-routine on terminators using the edge_transport binding
- Fix resource leak: retransmission timers for xgress instances not being shutdown when xgress
closed - Control channel metrics now available
- Fix potential deadlock on xgress close
- When closing due to fault notification, wait for data coming from remote to stop, not data from
both local and remote, since local writes may never stop, due to retransmission attempts - Add new config option to router
xgressCloseCheckInterval, which dictates for how long data flow
from the remote should have stopped before closing xgress after receiving fault limit nonefor Edge API Rest requests is now properly limited to 500 elements on list endpoints- The HTTP header
serveris now populated on all responses withziti-controller/vX.Y.Z
Control Channel Metrics
Note: This feature is only available if both controller and router are on 0.18.7 or higher.
The control channels between the controller and routers now generate metrics, including:
ctrl.<router id>.latencyctrl.<router id>.tx.bytesratectrl.<router id>.tx.msgratectrl.<router id>.tx.msgsizectrl.<router id>.rx.bytesratectrl.<router id>.rx.msgratectrl.<router id>.rx.msgsize
There is a new controller config file setting:
ctrlChanLatencyIntervalSecondswhich controls how often the latency probe is sent. Default
value: 10