Commit Graph

44 Commits

Author SHA1 Message Date
Mike Danese
3aa59f7f30 generated: run refactor 2020-02-07 18:16:47 -08:00
YuikoTakada
e98f4f3ef8 Use e2eskipper package in test/e2e/framework/ 2020-01-20 06:34:07 +00:00
yuxiaobo
cb07680ee9 remove TODO in test/e2e/framework/providers/gce/ingress.go
Signed-off-by: yuxiaobo <yuxiaobogo@163.com>
2020-01-14 10:43:03 +08:00
tanjunchen
f786cb07b7 test/e2e/: use framework.Equal() replace gomega.Expect(...).To(gomega.BeTrue()|BeFalse()) 2019-12-13 10:11:47 +08:00
Andrew Sy Kim
349749644f test/e2e: check both beta and zone label for getting cluster zone
Signed-off-by: Andrew Sy Kim <kiman@vmware.com>
2019-11-07 21:22:05 -05:00
Kubernetes Prow Robot
46a29a0cc3 Merge pull request #71674 from grayluck/firewall-event-msg
Change XPN firewall change msg. Should be required by security admin
2019-10-14 21:09:51 -07:00
Bob Killen
340eefe76b Prune inactive owners from test/e2e/framework/providers/vsphere/OWNERS. 2019-10-13 08:39:38 -04:00
yankaiz
bd03c3a096 Change XPN firewall change message, should be required by security admin.
Add l7lbSrcRngsFlag to gce_loadbalancer.go so that ingress can have
fewer source ranges for l7 health checks.
2019-09-30 11:19:42 -07:00
Justin SB
747d4481db e2e: on aws, tag volumes we want the cluster to mount
Locked down IAM configurations will prevent mounting of arbitrary
volumes, so when we create volumes that we intend the cluster to
mount, we must set the appropriate EC2 tags.
2019-09-30 00:51:49 -04:00
Dan Winship
71b02dd422 Fix up e2enode.GetReadySchedulableNodes, replace many uses of framework.GetReadySchedulableNodesOrDie
Remove the "OrDie" from the name (since it doesn't "or die") and add
an extra check that there is at least 1 node available, since many
callers already did that themselves, and many others should have.
2019-09-24 13:03:39 -04:00
WanLinghao
a6f5d99409 Refactor and clean up e2e framework utils. This patch handles test/e2e/framework/pv_util.go file 2019-09-18 17:57:13 +08:00
andyzhangx
313cc4278e test: fix azure disk e2e test failure 2019-09-04 10:30:25 +00:00
Kenichi Omichi
9e9c1709db Use log functions of core framework on sub p*
This makes sub packages of e2e test framework to use log functions
of core framework instead for avoiding circular dependencies.

NOTE: subpackage pod would make circular dependency if changing here.
      So we need to take care of it with another PR.
2019-08-23 19:50:47 +00:00
SataQiu
c60377c682 fix static check for test/e2e/framework 2019-08-21 17:28:36 +08:00
moriadry
4b8080dda8 Fix error collides with imported package name
Fix error collides with imported package name

fix

fix
2019-08-06 12:20:29 +08:00
draveness
c38ae01f8e feat: move service_util to separated package 2019-07-19 08:32:39 +08:00
Kubernetes Prow Robot
3f221551b6 Merge pull request #78728 from mborsz/firewall
Modify firewall rules names to make them shorter.
2019-07-01 07:23:34 -07:00
SataQiu
332be4b1e3 refactor: replace framework.Failf with e2elog.Failf 2019-06-19 17:52:35 +08:00
Jiatong Wang
b1c346c295 Move node related methods to framework/node package
- Add a package "node" under e2e/framework and alias e2enode;
- Rename some functions whose name have redundant string.

Signed-off-by: Jiatong Wang <wangjiatong@vmware.com>
2019-06-17 16:59:07 -07:00
Maciej Borsz
31f18c0a6d Modify firewall rules names to make them shorter. 2019-06-05 13:18:53 +02:00
Jorge Alarcon Ochoa
4969a05327 Refactored pod-related functions from framework/util.go
This a refactoring of framework/utils.go into framework/pod.

Signed-off-by: Jorge Alarcon Ochoa <alarcj137@gmail.com>
2019-05-30 09:30:26 -04:00
SataQiu
d3a902ff5b e2e refactor: cleanup Logf form framework/util 2019-05-24 16:39:46 +08:00
Richard Chen
2a70a0b424 Add an e2e test for running a gpu job interrupted by node recreation. 2019-05-16 11:41:01 -07:00
Walter Fender
796097ae40 Staging the GCE Cloud Provider
**What type of PR is this?**
/kind cleanup

**What this PR does / why we need it**:
Staging the GCE Cloud Provider as part of KEP [20190125-removing-in-tree-providers](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/20190125-removing-in-tree-providers.md). Staging repo setup here https://github.com/kubernetes/legacy-cloud-providers
Moves the GCE cloud provider implementation to staging.
This is in preparation for moving the cloud provider code out of tree entirely.
However we need it in staging while the code needs to be consumed both in/out of tree.

**Which issue(s) this PR fixes**:
Fixes #

**Special notes for your reviewer**:

**Does this PR introduce a user-facing change?**:

```
NONE
```

Updated import dependency tracking.
Factored in the cleanup from #77412
Minor fix to go.mod.
2019-05-07 13:17:52 -07:00
Kubernetes Prow Robot
d2b8f3e145 Merge pull request #77034 from atoato88/fix-golint-e2e-framework-providers-gce
Fix golint failures of e2e/framework/providers/gce/recreate_node.go
2019-05-06 19:17:40 -07:00
Mike Crute
6f5cf1a6e0 Staging legacy AWS cloud provider 2019-05-06 09:34:13 -07:00
Akihito INOH
2562d4d0fd Fix golint failures of e2e/framework/providers/gce/recreate_node.go
This fixes golint failures of the following file:

test/e2e/framework/providers/gce/recreate_node.go

And also, replaces functions using gomega with framework functions.
2019-05-03 07:20:37 +09:00
Stephen Augustus
2f74c90480 Staging the legacy Azure Cloud Provider
Signed-off-by: Stephen Augustus <saugustus@vmware.com>
2019-04-25 20:03:45 -04:00
Joachim Bartosik
74bd4d643a Detect zone of MIG in e2e VPA tests
I was running e2e VPA tests and some were failing because the tests
assume thata they're running on:
- zonal single-zone cluster, or
- regional multi-zone cluster.

And I was running them on regional, single-zoned cluster.

Change-Id: I110a70d2249f981b60cf76d1ad674ccfcedd8fb3
2019-04-24 16:11:53 +02:00
Davanum Srinivas
7b8c9acc09 remove unused code
Change-Id: If821920ec8872e326b7d85437ad8d2620807799d
2019-04-19 08:36:31 -04:00
Jiaying Zhang
8175579a0c add recreate node e2e test
Move recreate_node test to gce provider tests.
2019-04-12 16:00:19 -07:00
SataQiu
a232c3266d fix golint failures of e2e/framework/test_context.go 2019-03-29 14:41:24 +08:00
Minhan Xia
600e8b0eba make NEG tests more resilient to API failures and add more failure logging 2019-03-25 16:53:33 -07:00
Kenichi Omichi
da7c9f70c3 Fix golint failures under test/e2e/[..]/gce
This fixes golint failures under test/e2e/framework/providers/gce/.

Cleanup:
* FirewallTimeoutDefault is not used at all, so remove it.
* FirewallTestTcpTimeout, FirewallTestHttpPort and FirewallTestUdpPort
  are used at test/e2e/network/firewall.go only. So move them.
2019-03-22 15:59:17 +00:00
Kenichi Omichi
1fcab19821 Fix golint failures for e2e/[..]/kubemark 2019-03-05 20:55:00 +00:00
Sandeep Sunny
c4ef9ad765 Change to unblock vsphere e2e tests 2019-03-01 17:27:15 +05:30
Kubernetes Prow Robot
fb92681882 Merge pull request #74370 from oomichi/issue/74326
Register openstack provider for e2e test
2019-02-25 13:54:21 -08:00
Kenichi Omichi
5c3b0c1eef Register openstack provider for e2e test
Since the commit f3d79e152e
openstack provider has been denied on e2e test runner.
However there are storage e2e tests which are related to
openstack. So this adds the registration of openstack
provider for e2e test.
2019-02-21 21:15:36 +00:00
Kenichi Omichi
36b80a4c61 Fix golint failures on e2e/[..]/(aws|azure) 2019-02-20 19:11:53 +00:00
Kenichi Omichi
2635b6d95c Use framework.ExpectNoError() instead Expect()
The e2e test framework has ExpectNoError() for readable test code.
This replaces Expect(err).NotTo(HaveOccurred()) with it.
2019-02-15 16:52:57 +00:00
andrewsykim
596c6fbf03 e2e test for node deleted in cloud provider 2019-01-25 17:45:18 -05:00
walter
735ad9ed63 Fixed lint errors for pkg/cloudprovider/providers/gce.
Fixed minor issues.
Cleaned up from merge errors.
2018-10-29 11:52:24 -07:00
Patrick Ohly
97101a6a86 e2e: update bazel BUILD files
Generated via hack/update-bazel.sh.
2018-10-11 11:36:25 +02:00
Patrick Ohly
8b17db7e0c e2e: modular framework
Not all users of the E2E framework want to run cloud-provider specific
tests. By splitting out the code it becomes possible to decide in
a E2E test suite which providers are supported.

This is achieved in two ways:
- the framework calls certain functions through a provider
  interface instead of calling specific cloud provider functions
  directly
- tests that are cloud-provider specific directly import the
  new provider packages

The ingress test utilities are only needed by a few tests. Splitting
them out into a separate package makes the framework simpler for test
suites not using those tests.

Fixes: #66649
2018-10-11 11:16:11 +02:00