Repository navigation
Adopt the published scan-storage summary repair #5419
Description
🤖 Generated by the Agentic Engineer
Objective
Adopt the immutable scan-storage repair published from #5402 so vulnerability summaries retain consistent references when records are updated. Publication alone has not activated the repair.
Acceptance
- Verify the published image signature and provenance against the reviewed producer revision, then pin that immutable image without changing its signing policy.
- Retain recoverable scan-storage data and a reviewed rollback image; do not reset, delete or rewrite report payloads.
- Pass the existing publication, manifest, placement and integrity checks, then observe the intended image running after protected deployment.
- Verify repaired summary metadata against the stored reports and retain incomplete coverage as unknown. Scanner reference repair and remaining scan coverage stay tracked separately in Correct vulnerability manifest references in workload summaries #5403 and Reconcile Kubescape vulnerability summaries with the containers they describe #4263.
Part of #4263
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Priority
None yet
Effort
None yet
Projects
- Status
Activity
chore: agent-claim #5419 nonce=dde4e807fb47ed9bce894e996bdaa47e
fix(kubescape): bind revised storage image in the authorization ledger
devantler commentedon Oct 27, 2026
Post-deployment acceptance of #5420 failed: the new startup reconciler refuses the stored summary identities, and paired coverage still reports split metadata. The storage image is running and ready, but the data repair is not observed. #5405 remains held.
The API-visible identity pairs are present and consistent. A source mismatch is being reproduced: the storage API's internal summary type flattens ObjectMeta in SQLite metadata, while the repair decodes the versioned type's metadata wrapper. The original unit fixture uses that versioned type. The next regression will exercise the actual internal storage type and preserve the UID, creation-time, version-direction, scan-time, path-safety and compare-and-update guards.
chore: agent-claim #5419 nonce=9ea297fab3a984433fcde2f9eda1cf04