github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-30 15:05:27 +00:00
Code Issues Projects Releases Wiki Activity

Promote e2e to conformance tests for JobBackoffLimitPerIndex

Browse Source
This commit is contained in:
Michal Wozniak 2025-02-25 20:04:45 +01:00
parent a91ed902fe
commit d44ac38891
2 changed files with 37 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
test/conformance/testdata/conformance.yaml vendored
View File

@ -1109,6 +1109,17 @@
and delete the job. Job MUST be deleted successfully.
release: v1.15
file: test/e2e/apps/job.go
- testname: Ensure that all indexes are executed for an indexed job with backoffLimitPerIndex
despite some failing
codename: '[sig-apps] Job should execute all indexes despite some failing when using
backoffLimitPerIndex [Conformance]'
description: Create an indexed job and ensure that all indexes are either failed
or succeeded, depending on the end state of the corresponding pods. Pods with
odd indexes fail, while the pods with even indexes succeeded. Also, verify that
the number of failed pods doubles the number of failing indexes, as the backoffLimitPerIndex=1,
allowing for one pod recreation before marking that indexed failed.
release: v1.33
file: test/e2e/apps/job.go
- testname: Jobs, manage lifecycle
codename: '[sig-apps] Job should manage the lifecycle of a job [Conformance]'
description: Attempt to create a suspended Job which MUST succeed. Attempt to patch
@ -1119,6 +1130,15 @@
via a label selector.
release: v1.25
file: test/e2e/apps/job.go
- testname: Mark indexes as failed when the FailIndex action is matched in podFailurePolicy
codename: '[sig-apps] Job should mark indexes as failed when the FailIndex action
is matched in podFailurePolicy [Conformance]'
description: Create an indexed job with backoffLimitPerIndex, and podFailurePolicy
with the FailIndex action. Verify the failed pods matching the pod failure policy
result in marking the corresponding indexes as failed without restarts, despite
backoffLimitPerIndex > 0.
release: v1.33
file: test/e2e/apps/job.go
- testname: Jobs, completion after task failure
codename: '[sig-apps] Job should run a job to completion when tasks sometimes fail
and are locally restarted [Conformance]'
@ -1126,6 +1146,14 @@
the Job MUST execute to completion.
release: v1.16
file: test/e2e/apps/job.go
- testname: Terminate job execution when the maxFailedIndexes is exceeded
codename: '[sig-apps] Job should terminate job execution when the number of failed
indexes exceeds maxFailedIndexes [Conformance]'
description: Create an indexed job with backoffLimitPerIndex and maxFailedIndexes.
Verify the job execution is terminated as soon as the number of failed indexes
exceeds maxFailedIndexes.
release: v1.33
file: test/e2e/apps/job.go
- testname: ReplicaSet, is created, Replaced and Patched
codename: '[sig-apps] ReplicaSet Replace and Patch tests [Conformance]'
description: Create a ReplicaSet (RS) with a single Pod. The Pod MUST be verified

15
test/e2e/apps/job.go
View File

@ -593,13 +593,14 @@ done`}
})
/*
Testcase: Ensure that all indexes are executed for an indexed job with backoffLimitPerIndex despite some failing
Release: v1.33
Testname: Ensure that all indexes are executed for an indexed job with backoffLimitPerIndex despite some failing
Description: Create an indexed job and ensure that all indexes are either failed or succeeded, depending
on the end state of the corresponding pods. Pods with odd indexes fail, while the pods with even indexes
succeeded. Also, verify that the number of failed pods doubles the number of failing indexes, as the
backoffLimitPerIndex=1, allowing for one pod recreation before marking that indexed failed.
*/
ginkgo.It("should execute all indexes despite some failing when using backoffLimitPerIndex", func(ctx context.Context) {
framework.ConformanceIt("should execute all indexes despite some failing when using backoffLimitPerIndex", func(ctx context.Context) {
parallelism := int32(2)
completions := int32(4)
backoffLimit := int32(6) // default value
@ -627,12 +628,13 @@ done`}
})
/*
Testcase: Terminate job execution when the maxFailedIndexes is exceeded
Release: v1.33
Testname: Terminate job execution when the maxFailedIndexes is exceeded
Description: Create an indexed job with backoffLimitPerIndex and maxFailedIndexes.
Verify the job execution is terminated as soon as the number of failed
indexes exceeds maxFailedIndexes.
*/
ginkgo.It("should terminate job execution when the number of failed indexes exceeds maxFailedIndexes", func(ctx context.Context) {
framework.ConformanceIt("should terminate job execution when the number of failed indexes exceeds maxFailedIndexes", func(ctx context.Context) {
// we use parallelism=1 to make sure in the asserts only one pod was created
parallelism := int32(1)
completions := int32(4)
@ -712,13 +714,14 @@ done`}
})
/*
Testcase: Mark indexes as failed when the FailIndex action is matched in podFailurePolicy
Release: v1.33
Testname: Mark indexes as failed when the FailIndex action is matched in podFailurePolicy
Description: Create an indexed job with backoffLimitPerIndex, and podFailurePolicy
with the FailIndex action. Verify the failed pods matching the pod failure policy
result in marking the corresponding indexes as failed without restarts, despite
backoffLimitPerIndex > 0.
*/
ginkgo.It("should mark indexes as failed when the FailIndex action is matched in podFailurePolicy", func(ctx context.Context) {
framework.ConformanceIt("should mark indexes as failed when the FailIndex action is matched in podFailurePolicy", func(ctx context.Context) {
parallelism := int32(2)
completions := int32(2)
backoffLimit := int32(6) // default value