Monitoring, visualisation & management for Docker & Kubernetes
Mostly updates to dependencies, plus a couple of small improvements.
Thanks to everyone who contributed to this release: @gaby, @Kielek, @knrt10
This release fixes a bug on 'kubernetes describe' operations, where the probe would spin re-opening a connection to the UI again and again after the operation had finished.
Also removes some obsolete code which connected to the unsecured local kubelet port in Kubernetes; please update your configuration to a single probe to talk to Kubernetes for the whole cluster if you haven't already. Thanks to @CiMaol for this contribution.
This release brings a few bug-fixes and number of performance improvements, particularly in reducing the data sent when there are many socket connections between two endpoints.
The bump in version number reflects a change in wire protocol for this change in endpoints data, and also a change in the way active controls are encoded.
Thanks to everyone who contributed to this release: @DarthSett, @sarataha, @slalwani97 and @qiell.
This release is tagged 1.12 to signify a breaking change: it supports Kubernetes 'v1' object types that are needed for Kubernetes 1.16 and drops support for obsolete 'v1beta' types. #3691
Also the serialisation format changes: DNS data was accidentally renamed 'nodes' in release 1.11.6, and this release changes it back to 'DNS'. #3713
Thanks to everyone who contributed to this release: @bensooraj, @chandankumar4, @imazik, @oleggator and @qiell.
This is largely a performance improvement release: the biggest change is that the probe now publishes full reports one in three times; the rest are deltas which are much smaller hence use less CPU and memory in the app. #3677
Also a new debugging summary function in the app, exposed via http #3686
Some other small performance improvements:
Other changes:
This release contains a few fixes, one of which should improve resource usage on hosts that have a lot of TCP connections.
This is a bugfix release, which should improve some cases where reports get bigger and bigger over time due to Scope not seeing connections get closed.