Skip to content

Commit 7fe7135

Browse files
test(e2e): drop readiness asserts that HelmRelease Ready already covers
The qdrant and external-dns apps render their workload in a nested -system HelmRelease, and both suites already assert that HelmRelease Ready, which helm-controller reports only once the workload is up. Asserting readyReplicas on the same Deployment or StatefulSet again adds nothing, so those asserts keep only the instance-label pin. The vminstance PVC asserts follow a DataVolume Ready assert, and a DataVolume is not Ready before its PVC is Bound. Assisted-by: LLM Signed-off-by: Myasnikov Daniil <[email protected]>
1 parent 5415973 commit 7fe7135

3 files changed

Lines changed: 8 additions & 25 deletions

File tree

‎hack/e2e-chainsaw/external-dns/chainsaw-test.yaml‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -48,11 +48,11 @@ spec:
4848
resource:
4949
apiVersion: apps/v1
5050
kind: Deployment
51+
# Readiness is covered by the test-system HelmRelease above, so this only
52+
# checks the Deployment carries the nested release's instance label.
5153
metadata:
5254
labels:
5355
app.kubernetes.io/instance: test-system
54-
status:
55-
readyReplicas: 1
5656
---
5757
apiVersion: chainsaw.kyverno.io/v1alpha1
5858
kind: Test
@@ -100,8 +100,8 @@ spec:
100100
resource:
101101
apiVersion: apps/v1
102102
kind: Deployment
103+
# Readiness is covered by the test-prefix-system HelmRelease above, so this
104+
# only checks the Deployment carries the nested release's instance label.
103105
metadata:
104106
labels:
105107
app.kubernetes.io/instance: test-prefix-system
106-
status:
107-
readyReplicas: 1

‎hack/e2e-chainsaw/qdrant/chainsaw-test.yaml‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -105,13 +105,14 @@ spec:
105105
name: qdrant-test
106106
# Pins the label the catch collector selects on. Asserts are subset
107107
# matches, so this costs nothing and turns a silent drift of the
108-
# instance label into a red step instead of an empty capture.
108+
# instance label into a red step instead of an empty capture. Readiness
109+
# is covered by the qdrant-test-system HelmRelease above.
109110
spec:
110111
selector:
111112
matchLabels:
112113
app.kubernetes.io/instance: qdrant-test-system
113-
status:
114-
readyReplicas: 1
114+
# Stays: the reclaim step below only proves the PVC was reclaimed if it was
115+
# seen here first, an `error` on a PVC that never existed passes as well.
115116
- assert:
116117
timeout: 2m
117118
resource:

‎hack/e2e-chainsaw/vminstance/chainsaw-test.yaml‎

Lines changed: 0 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -40,15 +40,6 @@ spec:
4040
status:
4141
(conditions[?type == 'Ready']):
4242
- status: "True"
43-
- assert:
44-
timeout: 4m
45-
resource:
46-
apiVersion: v1
47-
kind: PersistentVolumeClaim
48-
metadata:
49-
name: vm-disk-test
50-
status:
51-
phase: Bound
5243
---
5344
apiVersion: chainsaw.kyverno.io/v1alpha1
5445
kind: Test
@@ -90,15 +81,6 @@ spec:
9081
status:
9182
(conditions[?type == 'Ready']):
9283
- status: "True"
93-
- assert:
94-
timeout: 4m
95-
resource:
96-
apiVersion: v1
97-
kind: PersistentVolumeClaim
98-
metadata:
99-
name: vm-disk-vmi-test
100-
status:
101-
phase: Bound
10284
- name: create-vminstance
10385
try:
10486
- apply:

0 commit comments

Comments
 (0)