Matt Moore
b750d1dddc
Drop the beta for GCR v2 images.
...
beta.gcr.io is no longer needed to pull through v2.
2015-11-14 12:19:02 -08:00
gmarek
82272989b7
Revert "Merge pull request #16358 from kubernetes/revert-16084-improve_e2e"
...
This reverts commit 465c5b0791
, reversing
changes made to 154923221f
.
2015-10-27 14:08:23 +01:00
Jerzy Szczepkowski
42d236fe59
Revert "All e2e tests should use NewFramework"
2015-10-27 13:14:57 +01:00
Clayton Coleman
a50fbd6636
All e2e tests should use NewFramework
...
Allows someone to replace createTestingNS consistently
2015-10-26 19:13:09 -04:00
Saad Ali
722c86aa50
Merge pull request #15948 from gmarek/fix-test
...
Add handling of old non-capitalized event reason to scheduler-predicates test
2015-10-23 12:06:14 -07:00
gmarek
bae456cb9d
Add handling of old non-capitalized event reason to scheduler-predicates test
2015-10-22 12:08:30 +02:00
Jeff Grafton
1ec0b09205
Ensure framework.afterEach is called to clean up resources
2015-10-20 21:33:27 -07:00
k8s-merge-robot
578d752174
Merge pull request #15772 from mesosphere/sttts-temporarily-fix-nodeselector-e2e-test
...
Auto commit by PR queue bot
2015-10-18 04:35:14 -07:00
Dr. Stefan Schimanski
d5aea32d07
Solve race between scheduler and kubelet about new node labels
2015-10-16 12:33:00 +02:00
gmarek
71fbef2e2d
Wait until all pods are running before starting tests
2015-10-13 13:00:14 +02:00
k8s-merge-robot
8580804f77
Merge pull request #15138 from mattmoor/limited-beta-rewrite
...
Auto commit by PR queue bot
2015-10-10 11:41:34 -07:00
Dr. Stefan Schimanski
cb00df9b28
Tag conformance tests with a [Conformance] string in the description
...
- remove skip list from conformance-test.sh and filter by the new tag
- remove experimental api tests from conformance test suite
- remove all tests from conformance test suite which are either
restricted to e.g. gce, gke, aws or require SSH
2015-10-09 23:14:43 +01:00
gmarek
3b11feda97
Change logging in scheduler_predicates e2e test
2015-10-07 11:10:48 +02:00
Matt Moore
eeb4eeb17c
Move pause and fluentd-elasticsearch to GCR v2.
...
This scopes down the initially ambitious PR:
https://github.com/kubernetes/kubernetes/pull/14960 to replace just
`pause` and `fluentd-elasticsearch` to come through `beta.gcr.io`.
The v2 versions have been pushed under new tags, `pause:2.0` and
`fluentd-elastisearch:1.12`.
NOTE: `beta.gcr.io` will still serve images using v1 until they are repushed with v2. Pulls through `gcr.io` will still work after pushing through `beta.gcr.io`, but will be served over v1 (via compat logic).
2015-10-06 16:39:07 -07:00
gmarek
42c6d716a5
Check for number of scheduled, not running nodes in scheduler_predicates test
2015-10-06 10:24:12 +02:00
Quinton Hoole
d8f821de1a
Port e2e/scheduler_predicates.go to e2e Framework.
...
Partially addresses #13503 , #13574 , #13828
2015-10-02 14:39:29 -07:00
Dr. Stefan Schimanski
6f2a1742ab
Add positive e2e test for NodeSelector
2015-09-26 09:46:56 +02:00
gmarek
1459a1523f
Add an option to modify timeout for namespace duration in e2e Framework
2015-09-24 10:32:34 +02:00
gmarek
393baa5157
Allow Density to run on non-GCE/GKE provider, rename deleteTestingNS
...
function.
2015-09-21 10:43:45 +02:00
Kris
f4ad00d9ae
Moving Status object to a common package
2015-09-17 14:09:53 -07:00
Quinton Hoole
97ddc9781c
Create fewer pods in Scheduler Predicates e2e test to speed things up.
2015-08-28 11:07:22 -07:00
Piotr Szczesniak
f6a3966abb
Added clean up to scheduler-predicates
2015-08-19 11:32:49 +02:00
Clayton Coleman
dcad51b90e
Deleting a namespace is insufficient to cleanup in e2e
...
Graceful deletion requires more time to terminate namespaces, and not
waiting for namespaces to delete causes scheduling errors
2015-08-18 17:36:00 -04:00
Kris Rousey
ae6c64d9bb
Moving everyone to unversioned client
2015-08-18 10:23:03 -07:00
gmarek
941ddc90b1
Fix SchedulerPredicates test after event reason rename
2015-08-14 11:20:37 +02:00
Mike Danese
8e33cbfa28
rewrite go imports
2015-08-05 17:30:03 -07:00
Alex Mohr
bcb6e1e107
Fix e2e scheduler_predicates.go to have 10 minute timeout instead of 2
...
minutes.
On an n1-standard-1 with only this test running, 2 minutes was enough
to create 189 pods out of the 300 desired. On slower VMs or with more
activity on the master (such as with parallel tests), 2 minutes is
nowhere near enough. This is a functional test, not a performance
test.
2015-08-04 22:59:30 -07:00
gmarek
36aff274f1
Add test that verifies that we don't allow resource overallocation on Nodes
2015-07-27 16:37:57 +02:00