Skip to main content

Latest Release Note

· 5 min read
note

This release note includes features:

  • that are already integrated in latest version,
  • that will be integrated in future release.

Upgrade risk

info
  • No compatibility issue 👍
  • No breaking changes 👍

Key changes

How to upgrade

  1. Use Helm chart 6.2.0 from repository
  2. Adjust global.version field value to latest in your values.yaml
  3. Deploy
tip

See Reference documentation for details.

Versions

Spider

New versions of Spider components:

ComponentVersionDocker tag
Helm chart6.2.0-
Analysis UI14.4latest
Controllers3.0latest
Gossipers7.7latest
Gociphers1.8latest
Back office-latest
Login UI-latest
Monitoring UI-latest

Dependencies

This operator is required on the Kube where Spider is installed.

DependencyVersion
Elastic Cloud for Kubernetes2 or 3

These components are set up in the correct versions by the Helm chart:

DependencyVersionDocker tag
Elastic stack9.1*9.1
Redis8.28-alpine
Traefik3.5v3.5

(*) Version 7 is still available and compatible for clusters still using ECK 2.

Compatibility

Spider has been successfully tested under these versions of dependencies:

3rd party softwareVersion
Helm3.14+
Kube1.24+

List of changes

Helm chart

✨ New features
  • New Pg Upload service to allow uploading Pg Coms.
  • Allow deploying a different Whisperer version than Controller one
  • Optional namespace-scoped ECK operator (v3.2): set elasticsearch.eck.enabled: true to let Spider install its own ECK when none is present, or when the existing one does not watch Spider's namespace. Preflight guards abort on conflict.
⚙️ Improvements
🐞 Bug fixes
  • Fix overloading the version of Controller or Gocipher

Analysis UI

✨ New features
  • UI redesign to enhance usability
  • Multi-protocol communications view (label: "All") — unified grid, sequence diagram, waterfall and stats showing HTTP and PostgreSQL communications together.
  • Waterfall view.
  • Drag and drop of widgets in Dashboard configuration
  • Drag and drop of columns in Columns selection
  • Drag and drop of actors in Sequence Diagram
  • Color scale to numeric columns in Grid
  • Save filters associated to view when switching views
  • Option to show Template in sequence diagram
  • Horizontal scroll to sequence diagram
  • Enhance pcap filter editor in Create Whisperer & Whisperer Capture Config tabs
    • Syntax highlighting
    • Parser
    • Templates
  • Add Playground in Whisperer Config to test Templates and Tags configuration
⚙️ Improvements
  • PSQL view
    • PSQL stats in Host details tab
    • Limit status code errors to code 400, that is the only one generated by the parser
    • Add JSON download to PgComs
🐞 Bug fixes

Controllers

✨ New features
⚙️ Improvements
  • Rewrite in Go for better scalability and stability of integration with Kubernetes
🐞 Bug fixes

Gossipers (Whisperers)

✨ New features
⚙️ Improvements
🐞 Bug fixes

Gociphers

✨ New features
⚙️ Improvements
🐞 Bug fixes

Back office

✨ New features
  • New Pg Upload service to allow uploading Pg Coms.
  • New MultiRead service (multi-read) to search HTTP and PostgreSQL communications in a unified view. Queries a single ES alias (spider-search-multicoms) that unions the HTTP and PG communication indices.
⚙️ Improvements
  • Allow service accounts to connect many times at once. Useful for automated tests, and surely for other stuff. Still logs a warning since last connection date could not be saved (OCC on Elastic).
  • Reduce CPU usage of status aggregation services (Whisps-Status-Agg, Ciphers-Status-Agg, Hosts-Agg). The instance sweep is now computed once per agent per polling batch instead of once per status message, reducing cost from O(N×K) to O(N+K). Whisperer batches in Hosts-Agg are also processed in parallel.
🐞 Bug fixes

Login UI

✨ New features
⚙️ Improvements
🐞 Bug fixes

Monitoring UI

✨ New features
⚙️ Improvements
🐞 Bug fixes

Online documentation

Main updated parts:

API impacts

note

This section informs about any impact on Spider API, so you may adjust your scripts.

Data impacts

note

The table below tells if there are data mapping changes in Elasticsearch indices, associated or not with migrations (Yes ✅ / No ❌).
Migration are automated at upgrade time, but they may leave unattended indices that you have to remove manually.

IndexDescriptionMigration
httpcoms & pgcomsNew alias for multi-com-