Skip to content

feat: federated ClamAV scanning across peer instances#77

Merged
hsinatfootprintai merged 1 commit intomainfrom
feat---add-containers-from-peers-to-scal
Apr 1, 2026
Merged

feat: federated ClamAV scanning across peer instances#77
hsinatfootprintai merged 1 commit intomainfrom
feat---add-containers-from-peers-to-scal

Conversation

@hsinatfootprintai
Copy link
Copy Markdown
Contributor

Each peer node now runs its own core-postgres + core-security containers and performs ClamAV scans locally. The primary aggregates scan results from all peers, enabling full security coverage across the fleet.

Changes:

  • Remove standalone mode PostgreSQL restriction so peers auto-provision core-postgres and core-security containers
  • Add peer forwarding methods for security reports, scan status, and scan triggers (ForwardSecurityReports, ForwardScanStatus, ForwardTriggerScan)
  • Rewrite SecurityServer to merge scan data from all peers in GetClamavSummary, ListClamavReports, GetScanStatus, and TriggerClamavScan
  • Add backend_id field to ClamavReport, ClamavContainerSummary, and ScanJob proto messages to identify which node owns each container
  • Add Node column to security UI table showing backend_id
  • Use protojson for parsing peer API responses (handles int64-as-string)

Each peer node now runs its own core-postgres + core-security containers
and performs ClamAV scans locally. The primary aggregates scan results
from all peers, enabling full security coverage across the fleet.

Changes:
- Remove standalone mode PostgreSQL restriction so peers auto-provision
  core-postgres and core-security containers
- Add peer forwarding methods for security reports, scan status, and
  scan triggers (ForwardSecurityReports, ForwardScanStatus, ForwardTriggerScan)
- Rewrite SecurityServer to merge scan data from all peers in
  GetClamavSummary, ListClamavReports, GetScanStatus, and TriggerClamavScan
- Add backend_id field to ClamavReport, ClamavContainerSummary, and
  ScanJob proto messages to identify which node owns each container
- Add Node column to security UI table showing backend_id
- Use protojson for parsing peer API responses (handles int64-as-string)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@hsinatfootprintai hsinatfootprintai merged commit 23c5011 into main Apr 1, 2026
3 checks passed
@hsinatfootprintai hsinatfootprintai deleted the feat---add-containers-from-peers-to-scal branch April 1, 2026 07:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants