From 0e17c48e350247eb46c538446a50c506251aed36 Mon Sep 17 00:00:00 2001 From: Matthias Bertschy Date: Mon, 7 Sep 2026 09:53:06 +0200 Subject: [PATCH] experiment(tests): enable CUSTOM_REST_ENABLED on the test storage deployment Component-tests have been failing widely (18-19/30 matrix jobs) since kubescape/helm-charts bumped storage.image.tag to v0.0.331, which enables kubescape/storage's single-writer write path by default (storage#393). That path serializes every Create/GuaranteedUpdate across all container profiles through one goroutine, collapsing write concurrency from up to 10-way (SqlitePoolSize) to strictly 1-way -- plausible cause of the sustained "context deadline exceeded" / "failed to create container profile, requeuing" errors seen throughout these test runs. This commit flips CUSTOM_REST_ENABLED (storage#387) on the test storage deployment to empirically check whether the new genericrest.Store-based REST path avoids the bottleneck. Code inspection of storage's pkg/apiserver/apiserver.go shows both REST implementations share the same containerProfileStorageImpl instance, so this is not expected to help, but is cheap to verify directly against CI before pursuing a fix that targets the single-writer path itself. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01LLN3CgGftcnAikV13qD6yJ --- tests/chart/templates/storage/deployment.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tests/chart/templates/storage/deployment.yaml b/tests/chart/templates/storage/deployment.yaml index 0bcb80d770..1fbdf238a1 100644 --- a/tests/chart/templates/storage/deployment.yaml +++ b/tests/chart/templates/storage/deployment.yaml @@ -39,6 +39,8 @@ spec: value: "{{ .Values.logger.level }}" - name: KS_LOGGER_NAME value: "{{ .Values.logger.name }}" + - name: CUSTOM_REST_ENABLED + value: "true" volumeMounts: - name: "data" mountPath: "/data"