Skip to content

Commit 1d8bea0

Browse files
committed
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 <[email protected]>
1 parent 7c06345 commit 1d8bea0

1 file changed

Lines changed: 11 additions & 2 deletions

File tree

‎packages/apps/harbor/tests/nginx_resources_test.yaml‎

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,8 @@ tests:
4141
- equal:
4242
path: spec.values.harbor.portal.resources.limits.cpu
4343
value: 500m
44+
- exists:
45+
path: spec.values.harbor.portal.resources.requests.memory
4446

4547
- it: keeps both sizes when the other components are resized
4648
template: templates/harbor.yaml
@@ -56,9 +58,16 @@ tests:
5658
memory: 1Gi
5759
jobservice:
5860
resourcesPreset: t1.medium
59-
trivy:
60-
resourcesPreset: t1.large
6161
asserts:
62+
- equal:
63+
path: spec.values.harbor.core.resources.limits.memory
64+
value: 128Mi
65+
- equal:
66+
path: spec.values.harbor.registry.registry.resources.limits.memory
67+
value: 1Gi
68+
- equal:
69+
path: spec.values.harbor.jobservice.resources.limits.memory
70+
value: 1Gi
6271
- equal:
6372
path: spec.values.harbor.nginx.resources.limits.memory
6473
value: 512Mi

0 commit comments

Comments
 (0)