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

19 Commits (657c01c695e3d09e2e57ff70d3acb706bbeb3a7f)

Author SHA1 Message Date
Anirudh 63e51dc66e PDB MaxUnavailable: e2e tests 2017-05-23 07:18:44 -07:00
Maciej Pytel adc1d6a428 Log error before failing in autoscaling e2e 2017-04-27 16:52:53 +02:00
Kubernetes Submit Queue fc843b09d5 Merge pull request #44853 from mwielgus/debug-autoscaler-e2e 
Automatic merge from submit-queue (batch tested with PRs 44741, 44853, 44572, 44797, 44439)

Print executed cmd in cluster autoscaler e2e tests

cc: @MaciekPytel @fgrzadkowski
 2017-04-25 01:56:37 -07:00
Marcin Wielgus 5082626cfc Print executed cmd in cluster autoscaler e2e tests 2017-04-24 16:12:47 +02:00
Kubernetes Submit Queue bf8bb433bf Merge pull request #44502 from MaciekPytel/ca_fix_e2e_2 
Automatic merge from submit-queue

Fix failing cluster-autoscaler e2e

Fix a panic in 2 CA e2e.
```release-note
```
 2017-04-14 15:38:59 -07:00
Mike Danese a05c3c0efd autogenerated 2017-04-14 10:40:57 -07:00
Maciej Pytel 96cf6079d1 Fix failing cluster-autoscaler e2e 2017-04-14 16:39:47 +02:00
Marcin Wielgus 1ee6667498 Cluster autoscaler broken nodes test fix 2017-04-13 10:56:04 +02:00
Marcin Wielgus c2f903ba6c Merge branch 'master' into disruptive 2017-04-11 17:42:48 +02:00
Marcin Wielgus 5eaba81126 Node failure tests for cluster autoscaler 2017-04-11 16:59:50 +02:00
Kubernetes Submit Queue 4ae6bd93c2 Merge pull request #44284 from MaciekPytel/ca_e2e_unflake 
Automatic merge from submit-queue (batch tested with PRs 43844, 44284)

Add a retry to cluster-autoscaler e2e

This should fix https://github.com/kubernetes/kubernetes/issues/44268.

The flake was caused by following sequence of events:
1. Cluster was at minimum size (3), some node was unneeded for a while.
2. Setup for some test (scale-down, failure) would increase node group size (to 5) and wait for new nodes to come up.
3. As soon as new node come up (cluster size 4) CA would scale-down the old unneeded node (setting node group size to 4).
4. Node group would not reach size 5 (as the target was now 4) and the test would timeout and fail.

This PR makes the setup monitor re-set the target node group size if the above scenario happens.
 2017-04-11 06:42:15 -07:00
Maciej Pytel c0c77d7681 Add a retry to cluster-autoscaler e2e 2017-04-10 19:16:30 +02:00
Maciej Pytel 18ab7314bc Fix Cluster-Autoscaler e2e on testgrid 2017-04-06 11:20:23 +02:00
Maciej Pytel 67f5ba0004 Cluster-Autoscaler e2e to catch unnecessary scale-ups 
This fails (with large probability, as issue is not 100% deterministic)
on 0.5.0, catching the bug in this version.
 2017-04-05 15:23:29 +02:00
Maciej Pytel 1c9f64c760 e2e for cluster-autoscaler unhealthy cluster handling 
Moved testUnderNetworkFailure function to framework,
so it can be reused.
 2017-04-04 14:36:44 +02:00
Maciej Pytel 2630cefcce Add retries in cluster-autoscaler e2e 2017-04-04 10:28:24 +02:00
Maciej Pytel 0d666e1fcd Cluster-autoscaler multistep node drain e2e 2017-04-04 10:28:24 +02:00
Marcin Wielgus 3f7bf0206f Extract commonly used functions from e2e/resize_nodes.go to e2e/framework 2017-04-04 00:01:20 +02:00
Marcin Wielgus dac7b3e268 Move autoscaling e2e tests to a separate directory 2017-04-03 16:40:34 +02:00