a55c71db4d
test/e2e
2016-11-23 15:53:09 -08:00
35626b2a7b
Wait for all Nodes to be schedulable before running e2e tests
2016-11-17 16:43:35 +01:00
0f9c0678b7
Update API server CPU constraints in the density test
2016-11-16 16:33:53 +01:00
69069cd157
Fix resource constraints in density test
2016-11-10 10:21:27 +01:00
024299780e
Stricter timeouts for nodePort curling
2016-11-03 22:31:39 -07:00
bd21b0312b
Create multiple clients in Density test and remove unused 'interval'
2016-11-02 11:20:24 +01:00
2e011d3097
Update density.go
2016-11-02 09:16:20 +01:00
b6a5992ee5
Fix density test in large clusters
2016-11-01 11:03:21 +01:00
30c78c8ab3
Create multiple namespaces in the Density test
2016-10-28 13:50:39 +02:00
b8a83b983f
Remove outdated parts of density test
2016-10-27 11:37:26 +02:00
ef7850e3bc
Merge pull request #35395 from jayunit100/density-log-verify
...
Automatic merge from submit-queue
dont fail if metrics arent working in density
fixes #35369
2016-10-25 11:01:54 -07:00
33ebe1f18b
Merge pull request #34905 from ingvagabund/client-to-clientset
...
Automatic merge from submit-queue
Replace client with clientset
Replace client with clientset in some places
Fixes : #34637
2016-10-24 05:38:43 -07:00
0940b6297d
dont fail if metrics arent working in density
2016-10-24 08:36:56 -04:00
aeba0f1dc4
Change a type of collection of strategies for NodePreparer
2016-10-24 11:47:36 +02:00
4b21b71612
Use TestNodePreparer in Density test
2016-10-24 10:19:27 +02:00
4fde09d308
Replace client with clientset in code
2016-10-23 22:00:35 +02:00
7a573d4d3c
Add test_list command, to enumerate unit and e2e tests.
...
This uses go/parser and go/ast to analyze all test files in ~1 second.
It only recognizes a few simple structures that the tests all have, and
modifies a few tests to fit expected structure better.
This is part of an effort to ensure all tests have owners, by having a
verify check to catch new tests being added without an owner.
2016-10-17 15:56:33 -07:00
b1b8e9e403
Merge pull request #34544 from gmarek/split
...
Automatic merge from submit-queue
Move RunRC-like functions to test/utils
Ref. #34336
cc @timothysc - the "move" part of the small refactoring. @jayunit100
2016-10-14 07:22:38 -07:00
00a437bb5c
Fix ginkgo panic in density test
2016-10-13 14:12:41 +02:00
7681a1bdff
Move RunRC-like functions to test/utils
2016-10-12 15:06:56 +02:00
1aff115f44
Make logging function injectable in RCConfig
2016-10-11 16:46:33 +02:00
48ac4d549d
change e2e scale to avoid adapter
2016-09-26 07:58:01 -04:00
767bc90a20
Fix removing RCs in density test
2016-09-16 13:13:02 +02:00
a765d59932
move informer and controller to pkg/client/cache
...
Signed-off-by: Mike Danese <mikedanese@google.com>
2016-09-15 12:50:08 -07:00
a6e8789194
Relax the CPU constraint for L7 lb
2016-09-12 10:42:44 +02:00
4051a2f8ea
Increase the threshold for apiserver CPU for 500 node kubemark
2016-09-05 09:48:25 +02:00
8a44cb5c7b
Merge pull request #31683 from gmarek/kubemark-5
...
Automatic merge from submit-queue
Tune kubemark-5 resource constraints
Ref. #31105
2016-08-30 01:35:38 -07:00
6ab61d7a97
Tune kubemark-5 resource constraints
2016-08-30 09:34:47 +02:00
c106646d32
Tweak resource constraints in scalability tests
2016-08-26 10:19:45 +02:00
1e7545393f
Merge pull request #30979 from m1093782566/fix-unnecessary-delete-rc-requests
...
Automatic merge from submit-queue
[e2e density test] Fix unnecessary Delete RC requests when not running latency test
As the following code block
https://github.com/kubernetes/kubernetes/blob/master/test/e2e/density.go#L666-L670
shows, after running each density test case, it will attempt to delete "additional replication controllers" even though there is **no additional replication controller**.
When we are not running latency test, API Server will return "404 error code". So, I propose to move the above code block inside thedetermine statementsif `itArg.runLatencyTest{ }` , looks like:
```
if itArg.runLatencyTest {
...
for i := 1; i <= nodeCount; i++ {
name := additionalPodsPrefix + "-" + strconv.Itoa(i)
c.ReplicationControllers(ns).Delete(name, nil)
}
}
```
In this way, removing RC will be executed only if we set `itArg.runLatencyTest` to be `true`. It can avoid post some necessary requests to API Server.
Issuse is #30977
2016-08-22 07:00:52 -07:00
943860b3c7
Tweak resource consumption in density test
2016-08-22 10:03:45 +02:00
09668823a9
fix unnecessary delete rc requests
...
Change-Id: I5e7813acebd0607c049d521cce559b96708be1a2
2016-08-19 16:14:50 +08:00
47e0d4dc89
fix e2e test pause image hard code
...
Change-Id: I30ee8d5da96b6de42cf7d308776dcb9606d67dfb
2016-08-19 12:11:28 +08:00
d3d5f88880
Make sure that provider is set when we create resource constraints in the density test
2016-08-18 13:41:17 +02:00
715f4f0978
Merge pull request #30856 from wojtek-t/fix_density_part_1
...
Fix l7 constraints in density test
2016-08-18 12:12:29 +02:00
bd6c5f4f57
Fix l7 constraints in density test
2016-08-18 11:30:03 +02:00
59b7a05e15
Fix resource constraint checking in Density test
2016-08-17 14:12:41 +02:00
3688a78769
let load and density e2e tests use GC if it's on
2016-08-11 11:48:20 -07:00
e7d01097dc
Merge pull request #29971 from caesarxuchao/fix-kubectl-rolling-update-with-gc
...
Automatic merge from submit-queue
[GarbageCollector] Fix kubectl rolling-update to work with GC
This changes the order of the [Rename()](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/rolling_updater.go#L532 ) function. After the change, Rename() first deletes the old RC and orphans its pods, then creates the new RC, which will then have a chance to adopt the orphaned pods.
This also fixes the "should support rolling-update to same image" [test](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/kubectl.go#L915 ) when the garbage collector is on.
Here is the detailed explanation on why the test would have failed:
`kubectl rolling-update` will [rename](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/rolling_updater.go#L532-L546 ) the RC. It first creates the an identical RC (including spec.selectors) with the new name, then it deletes the existing RC. When GC is turned on, the newly created RC cannot adopt the existing pod, because it has a controllerRef pointing to the exising RC, so the new RC will create new pods and expect to see the creation. However, the new RC and the old RC have the same selector, so sometimes the old RC, instead of the new RC, has its [expectation lowered](https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/replication/replication_controller.go#L346-L362 ), the new RC's expectation will stuck forever. The e2e test then times out when executing `kubectl delete newRC`, because there is the new RC will not scale down as its expectation is not fulfilled.
A side-note, we should fix [rm.getPodController()](https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/replication/replication_controller.go#L346 ) to respect pod's controllerref, that will prevent similar bugs.
Also note that an old version `kubectl rolling-update` will not work with the GC. We cannot fix that.
2016-08-04 20:48:10 -07:00
fb72b50135
Added test to density that will run maximum capacity pods on all nodes
2016-08-04 11:46:22 -04:00
96c84303bd
fix kubectl rolling-update when GC is enabled
2016-08-03 15:57:03 -07:00
c495397cae
Refactor uuid into its own pkg
2016-07-30 00:07:02 -04:00
656ea8f98f
test/e2e: plug time.Ticker resource leak.
...
This commit ensures that `logPodStartupStatus` does not leak
running `time.Ticker` instances. Upon termination of the consuming
routine, we stop the ticker.
2016-07-18 16:26:42 +02:00
ef0c9f0c5b
Remove "All rights reserved" from all the headers.
2016-06-29 17:47:36 -07:00
61fb527801
Merge pull request #26631 from gmarek/constraints
...
Automatic merge from submit-queue
Revert revert of adding resource constraints for master components in density tests
The problem was the time when resource constraints were generated. It turns out that the provider is not set there. This version should work.
cc @roberthbailey @alex-mohr
2016-06-02 05:15:55 -07:00
2a5883fc3a
Wait for all nodes to be schedulable in scalability tests
2016-06-02 10:20:59 +02:00
8a05258070
Revert "Merge pull request #26356 from kubernetes/revert-25752-resource-limits"
...
This reverts commit 60c2ab4995965e8dce12
2016-06-01 15:09:32 +02:00
04bdd37bc4
Merge pull request #25972 from luxas/remove_arch_constants
...
Automatic merge from submit-queue
Use pause image depending on the server's platform when testing
Removed all pause image constant strings, now the pause image is chosen by arch. Part of the effort of making e2e arch-agnostic.
The pause image name and version is also now only in two places, and it's documented to bump both
Also removed "amd64" constants in the code. Such constants should be replaced by `runtime.GOARCH` or by looking up the server platform
Fixes : #22876 and #15140
Makes it easier for: #25730
Related: #17981
This is for `v1.3`
@ixdy @thockin @vishh @kubernetes/sig-testing @andyzheng0831 @pensu
2016-05-28 04:48:59 -07:00
79ca1911e1
Removed all pause image constant strings, now the pause image is chosen by arch. Part of the effort of making e2e arch-agnostic
2016-05-26 19:16:43 +03:00
a2011cdf42
Revert "Add resource limits for master resources in density test"
2016-05-26 16:35:48 +02:00
Chao Xu