github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-25 04:33:26 +00:00
Code Issues Projects Releases Wiki Activity

Fix conformance testdata

Browse Source
This commit is contained in:
Caleb Woodbine 2020-03-02 14:23:29 +13:00
parent 67fb7c5989
commit 51d3f64b81
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1708,15 +1708,6 @@
be evicted if the taint is removed before toleration time ends. be evicted if the taint is removed before toleration time ends.
release: v1.16 release: v1.16
file: test/e2e/scheduling/taints.go file: test/e2e/scheduling/taints.go
- testname: Pod preemption verification
codename: '[sig-scheduling] PreemptionExecutionPath runs ReplicaSets to verify preemption
running path [Conformance]'
description: Four levels of Pods in ReplicaSets with different levels of Priority,
restricted by given CPU limits MUST launch. Priority 1 - 3 Pods MUST spawn first
followed by Priority 4 Pod. The ReplicaSets with Replicas MUST contain the expected
number of Replicas.
release: v1.18
file: test/e2e/scheduling/preemption.go
- testname: Scheduler, resource limits - testname: Scheduler, resource limits
codename: '[sig-scheduling] SchedulerPredicates [Serial] validates resource limits codename: '[sig-scheduling] SchedulerPredicates [Serial] validates resource limits
of pods that are allowed to run [Conformance]' of pods that are allowed to run [Conformance]'
@ -1767,6 +1758,15 @@
same node if the HostIP or Protocol is different. same node if the HostIP or Protocol is different.
release: v1.16 release: v1.16
file: test/e2e/scheduling/predicates.go file: test/e2e/scheduling/predicates.go
- testname: Pod preemption verification
codename: '[sig-scheduling] SchedulerPreemption [Serial] PreemptionExecutionPath
runs ReplicaSets to verify preemption running path [Conformance]'
description: Four levels of Pods in ReplicaSets with different levels of Priority,
restricted by given CPU limits MUST launch. Priority 1 - 3 Pods MUST spawn first
followed by Priority 4 Pod. The ReplicaSets with Replicas MUST contain the expected
number of Replicas.
release: v1.18
file: test/e2e/scheduling/preemption.go
- testname: ConfigMap Volume, text data, binary data - testname: ConfigMap Volume, text data, binary data
codename: '[sig-storage] ConfigMap binary data should be reflected in volume [NodeConformance] codename: '[sig-storage] ConfigMap binary data should be reflected in volume [NodeConformance]
[Conformance]' [Conformance]'