This release brings many configuration and deployment enhancements as well as the general availability of Network Usage monitoring.

I am excited to announce a significant enhancement to Spider: the introduction of Network Usage Monitoring 💪

This new feature empowers users with comprehensive insights into network communications within their Kubernetes clusters, facilitating system discovery, performance optimization, and anomaly detection.

Spider default PEM format has been upgraded to PKCS#8.

Spider values is now more compatible with ArgoCd.

Spider now includes a new circuit breaker to limit its impact: a throughput limiter.

When set, the Whisperer checks the rate of capture packets continuously and discards packets once the throughput is reached.

Spider now facilitate local development with the introduction of local agents.

Any user may be given local agents (Controller, Whisperer, Gocipher) to observe the communications of his developments running locally.

This release brings more observability, stability and diversity on Spider agents:

• Remote logs access
• Backoff on failed attachments
• Local agents

It also restores UDP capture that was failing lately.

We had the need recently to capture DNS calls to try to get an idea why sometimes DNS resolving fails on Kube.
Except that Spider had a regression on UDP capture, and it was not any more possible to save UDP packets on the back office.

I fixed this and added a few quick features for DNS parsing.

Here comes a new release of Spider Controller with a bunch of improvements:

• Lists Gociphers & Sidecar Whisperers
• Allows getting logs from Controller, Attachments, Sidecars & Gociphers
• Provides Sidecar Whisperers to Gociphers to allow TLS deciphering on their captured data
• When an Ephemeral Whisperer fails twice in 5 minutes, the Controller stops restarting it to avoid overloading the POD manifest