Yan Bondarenko 1d8bea039b test(harbor): check that the resized components reach the release ...

The case that resizes the other components looked only at nginx and
the portal, so it would keep passing if those overrides stopped
reaching the nested release, and then it could not catch nginx or the
portal following another component's values. It now checks the core,
registry and jobservice limits it sets and leaves trivy alone, as
nothing in the case reads it. The portal case also checks its memory
request, as the nginx case does.

Assisted-by: LLM
Signed-off-by: Yan Bondarenko <202671653+yankawai@users.noreply.github.com>

2026-10-21 13:13:56 +03:00

..

cleanup_hook_test.yaml

fix(apps): bound the wait the cleanup hooks now perform

2026-09-17 21:49:51 +03:00

host_guard_harbor_cr_test.yaml

test(charts): isolate guard coverage for every guarded template

2026-09-28 18:32:49 +03:00

host_guard_httproute_test.yaml

test(charts): isolate guard coverage for every guarded template

2026-09-28 18:32:49 +03:00

host_guard_test.yaml

fix(charts): fail fast on empty tenant apex in host composition

2026-09-28 15:14:45 +03:00

ingress_management_whitelist_test.yaml

fix(harbor): refuse managementWhitelist entries that are not addresses

2026-09-24 15:52:35 +03:00

ingress_wildcard_test.yaml

fix(ingress): keep tls section in operator wildcard mode

2026-06-10 03:18:42 +03:00

install_retry_test.yaml

fix(harbor): retry the nested system install instead of uninstalling it

2026-08-08 00:12:53 +03:00

jobservice_storageclass_test.yaml

test(harbor): select hook and release documents by kind, not by index

2026-08-08 03:09:46 +03:00

nginx_resources_test.yaml

test(harbor): check that the resized components reach the release

2026-10-21 13:13:56 +03:00