nano v2.0.24
nano v2.0.24 hotfix: Agent Lane works and its port is locked to Agent Lane tokens, single-host upgrades pass preflight, and large parsers deploy on slower hosts.
v2.0.24 includes everything in v2.0.23. It is a security release. Every Self-run install should upgrade.
To upgrade, follow Upgrade a self-hosted deployment. v2.0.20 is a required stop: installs on a release older than v2.0.20 upgrade to v2.0.20 first, then to v2.0.24. If you are on v2.0.23, scripts/nano upgrade may fail its preflight on a single-host install. Use the install.sh steps on the v2.0.23 page for this one upgrade. From v2.0.24 on, scripts/nano upgrade works.
Security
- Only Agent Lane tokens can sign in on the Agent Lane port. On Kubernetes, ClickHouse's built-in
defaultandoperatorusers are now limited to in-cluster networks while Agent Lane is on. On every install, Agent Lane refuses to turn on, or to create tokens, if any other ClickHouse user can be reached from the agent networks, or if a ClickHouse node can't be checked. SIEM Health reports any such user as critical. The backup user is now kept on internal networks only. - Parser test code runs only inside the limited worker. Testing or validating a parser no longer compiles it inside the API process. Each user gets at most one of the test workers at a time.
Fixes
- Agent Lane tokens stopped working about a minute after you created them. A background job didn't receive the Agent Lane settings and removed each token's access. Every Agent Lane setting now reaches both services that need it, on Docker Compose, multi-server installs and Kubernetes. Agent Lane is ready to use from this release.
scripts/nano upgradefailed its preflight on single-host installs. It validated the Vector configuration differently from how Vector runs it. It now uses the same settings as the running container.- Large parsers failed to deploy on slower hosts. Sysmon, Cisco ASA and CrowdStrike could hit the time limit of the sample test that runs before a deploy. Deploys now have their own, larger time limit, and wait for a free test worker instead of failing.
- Kubernetes: a parser deploy was reported done before every Vector pod had it. A deploy is now confirmed only when every Vector pod runs the new configuration. A pod that rejects it is reported.
- Monitoring: the "ingest stalled" alert fired on healthy, idle installs. It now ignores nano's own internal test events.
- Custom enrichment results took up to an hour to apply. They now apply right after a run.
Upgrade notes
- Required stop at v2.0.20. See above.
- Upgrade with the release, not by editing image tags. On Docker Compose, use
scripts/nano upgradeor re-runinstall.shfrom the new bundle. On Kubernetes, usehelm upgradewith the new chart.
nano v2.0.25
nano v2.0.25: Evidence Pack compliance exports, an SBOM for every release, and security updates to PostgreSQL, ClickHouse and other components.
nano v2.0.23
nano v2.0.23: Agent Lane gives AI agents read-only, audited ClickHouse access over their own listener, and Vector no longer drops events when ClickHouse refuses its writes.