2026.01.14 Release Note
This version introduces PostgreSQL parsing as a first citizen of Spider.
Upgrade risk
- No compatibility issue 👍
Breaking change!
As PostgreSQL parsing is now a first citizen of Spider, Parsing HTTP by default on all TCP ports is not anymore the
default configuration of Whisperers.
This might impact your Whisperers if you are using the default configuration.
You should check and adjust it if needed.
This change was required:
- to avoid parsing HTTP on PostgreSQL ports, which leads to many parsing errors logs.
- to avoid useless CPU load and reduce your bill 😉
- for consistency on PostgreSQL parsing settings, which is not to parse by default on all TCP ports.
... That change broke my regression tests 😅
Key changes
- PostgreSQL parsing in streaming
- Bug fixes for even better resiliency.
How to upgrade
- Use Helm chart
6.0.0from repository - Adjust
global.versionfield value to2026.01.14in your values.yaml - Deploy
To activate PostgreSQL parsing, set flips.postgresqlParsing to true in your values.yaml.
See Reference documentation for details.
Versions
Spider
New versions of Spider components:
| Component | Version | Docker tag |
|---|---|---|
| Helm chart | 6.0.0 | - |
| Analysis UI | 13.0 | 2026.01.14 |
| Controllers | 2.3 | 2026.01.14 |
| Gossipers | 7.7 | 2026.01.14 |
| Gociphers | 1.8 | 2026.01.14 |
| Back office | - | 2026.01.14 |
| Login UI | - | 2026.01.14 |
| Monitoring UI | - | 2026.01.14 |
Dependencies
This operator is required on the Kube where Spider is installed.
| Dependency | Version |
|---|---|
| Elastic Cloud for Kubernetes | 2 or 3 |
These components are set up in the correct versions by the Helm chart:
| Dependency | Version | Docker tag |
|---|---|---|
| Elastic stack | 9.1* | 9.1 |
| Redis | 8.2 | 8-alpine |
| Traefik | 3.5 | v3.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 software | Version |
|---|---|
| Helm | 3.14+ |
| Kube | 1.24+ |
List of changes
Helm chart
| ✨ New features |
|
|---|---|
| ⚙️ Improvements | |
| 🐞 Bug fixes |
|
Analysis UI
| ✨ New features |
|
|---|---|
| ⚙️ Improvements |
|
| 🐞 Bug fixes |
|
Controllers
| ✨ New features | |
|---|---|
| ⚙️ Improvements |
|
| 🐞 Bug fixes |
|
Gossipers (Whisperers)
| ✨ New features | |
|---|---|
| ⚙️ Improvements |
|
| 🐞 Bug fixes |
Gociphers
| ✨ New features | |
|---|---|
| ⚙️ Improvements |
|
| 🐞 Bug fixes |
|
Back office
| ✨ New features |
|
|---|---|
| ⚙️ Improvements |
|
| 🐞 Bug fixes |
|
Login UI
| ✨ New features | |
|---|---|
| ⚙️ Improvements | |
| 🐞 Bug fixes |
Monitoring UI
| ✨ New features |
|
|---|---|
| ⚙️ Improvements | |
| 🐞 Bug fixes |
Online documentation
Main updated parts:
- Reference values.yaml - Activate PostgreSQL parsing
- Whisperer parsing configuration for PostgreSQL
- PostgreSQL communication details
- New services configuration
- Summary monitoring screen update
- Parsing monitoring screen update
API impacts
This section informs about any impact on Spider API, so you may adjust your scripts.
- Components lists
- Pg Read API
Data impacts
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.
| Index | Description | Migration |
|---|---|---|
| spider-pgcom-upload-* | Stores uploaded pg coms metadata | New |
| spider-pgcom-streaming-* | Stores streamed pg coms metadata | New |
| spider-pgcomcontent-upload-* | Stores uploaded pg coms contents | New |
| spider-pgcomcontent-streaming-* | Stores streamed pg coms contents | New |
| spider-pgparsing-upload-* | Stores parsing log for uploaded pg coms | New |
| spider-pgparsing-streaming-* | Stores parsing log for streamed pg coms | New |
| spider-parsing-status-pgparsing-streaming-* | Stores parsings status for streamed pg coms | New |