github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
53,441 Commits
32 Branches
881 Tags
633 MiB
Commit Graph

28 Commits (d5dcec5218da77b59e36a9a6aee05ff510dd6d91)

Author SHA1 Message Date
xiangpengzhao 1c4dbcf5ca Replace hard-code "cpu" and "memory" to consts 2017-08-16 16:37:50 +08:00
Michael Taufen 24bab4c20f move KubeletConfiguration out of componentconfig API group 2017-08-15 08:12:42 -07:00
Chao Xu 60604f8818 run hack/update-all 2017-06-22 11:31:03 -07:00
Chao Xu f4989a45a5 run root-rewrite-v1-..., compile 2017-06-22 10:25:57 -07:00
Chao Xu 4f9591b1de move pkg/api/v1/ref.go and pkg/api/v1/resource.go to subpackages. move some functions in resource.go to pkg/api/v1/node and pkg/api/v1/pod 2017-04-17 11:38:11 -07:00
David Ashpole ac612eab8e eviction manager changes for allocatable 2017-03-02 07:36:24 -08:00
Michael Taufen 945d223738 Set custom threshold for memory eviction test 2017-02-03 16:48:34 -08:00
Dr. Stefan Schimanski bc6fdd925d pkg/api/resource: move to apimachinery 2017-01-29 21:41:44 +01:00
Clayton Coleman 469df12038
refactor: move ListOptions references to metav1 2017-01-23 17:52:46 -05:00
Clayton Coleman 9a2a50cda7
refactor: use metav1.ObjectMeta in other types 2017-01-17 16:17:19 -05:00
deads2k 6a4d5cd7cc start the apimachinery repo 2017-01-11 09:09:48 -05:00
Wojciech Tyczynski a9ec31209e GetOptions - fix tests 2016-12-09 09:42:01 +01:00
Chao Xu 29400ac195 test/e2e_node 2016-11-23 15:53:09 -08:00
David Ashpole f6224590f7 Test Container Garbage Collection 2016-11-15 09:15:31 -08:00
Jan Chaloupka 4fde09d308 Replace client with clientset in code 2016-10-23 22:00:35 +02:00
Random-Liu ed411c9042 Add image white list, images in white list will be prepulled, and 
only images in white list could be used in the test. Currently only
enabled in node e2e test.
 2016-09-19 14:39:23 -07:00
Michael Taufen 28db03869b Fix memory eviction test parameters. Those parameters should NOT have come through in b9f0bd95 2016-09-12 12:01:53 -07:00
Michael Taufen b9f0bd959e Log the following items in memory eviction test: 
- memory working set
- pressure condition
- events for the default and test namespaces, after the test completes
 2016-09-09 13:42:26 -07:00
Michael Taufen 3ad9a1e423 Move wait for pressure to subside to AfterEach so we still wait if the test for eviction order fails 2016-09-01 14:39:43 -07:00
Michael Taufen b3e9875fcc Wait before trying to start a new pod after the eviction test 
This should stop the test from flaking while we figure out why there is
a mismatch between the reported pressure condition and the eviction
manager's decision to evict due to memory pressure.
 2016-08-31 10:42:20 -07:00
Michael Taufen d0f84dd4e7 podName must be lowercase 2016-08-26 15:12:34 -07:00
Michael Taufen aa1d273584 Wait for the memory pressure condition to be absent before finishing the memory eviction test 2016-08-26 10:15:28 -07:00
Dawn Chen 24e81af7b3 Revert "Avoid disk eviction node e2e test using up all the disk space" 2016-08-26 08:59:42 -07:00
bindata-mockuser d0577e7c74 Avoid disk eviction node e2e test using up all the disk space 2016-08-24 22:07:58 -07:00
Kubernetes Submit Queue 8c430c2fd7 Merge pull request #30476 from mtaufen/eviction_fix 
Automatic merge from submit-queue

Wait for memory to be reclaimed after node_e2e MemoryEviction test

This helps prevent interference with other tests that run immediately after the MemoryEviction test.

/cc @Random-Liu @coufon
 2016-08-19 17:22:05 -07:00
Michael Taufen a227ce42f2 Wait for memory to be reclaimed after node_e2e MemoryEviction test 
This helps prevent interference with other tests that run immediately
after the MemoryEviction test.
 2016-08-19 13:58:03 -07:00
Michael Taufen 8575b73298 Label MemoryEviction [Disruptive] 2016-08-11 15:21:54 -07:00
Michael Taufen 736f1cb7c3 Node e2e memory eviction test 
This test creates three pods with QoS of besteffort, burstable, and
guaranteed, respectively, which each contain a container that tries to
consume almost all the available memory at a rate of about 12Mi/10sec.

The expectation is that eviction will be initiated when the hard
memory.available<250Mi threshold is triggered, and that eviction will proceed
in the order of besteffort, then burstable. Since guaranteed pods should
only be evicted if something charged to the host uses more resources
than were reserved for it, we currently end the test when besteffort and
burstable have both been evicted.

Note that this commit also sets --eviction-hard=memory.available<250Mi
to enable eviction during tests.
 2016-08-08 15:59:51 -07:00