add e2e network policy test

[lzhecheng]

This PR is to add a simple e2e network policy test. The testing network policy only allows traffic from pod with correct label.

[antrea-bot]

Thanks for your PR.
Unit tests and code linters are run automatically every time the PR is updated.
E2e tests can only be triggered by a member of the vmware-tanzu organization. Regular contributors to the project should join the org.

The following commands are available:

• /test-e2e: to trigger e2e tests. This command can only be run by members of the vmware-tanzu organization
• /skip-e2e: to skip e2e tests. This command can only be run by members of the vmware-tanzu organization

[vmwclabot]

@lzhecheng, you must sign our contributor license agreement before your changes are merged. Click here to sign the agreement. If you are a VMware employee, read this for further instruction.

[lzhecheng]

/test-e2e

[lzhecheng]

/test-e2e

[tnqn]

@lzhecheng thanks for working on this, but is the test case different from https://github.com/kubernetes/kubernetes/blob/master/test/e2e/network/network_policy.go? If not, I think we don't need to add duplicate ones, we should only add cases not covered by upstream tests. We can first enable the upstream ones.

[antoninbas]

If the K8s network policy tests can be run as part of the Kind CI (#137) and complete in a few minutes, then I am also in favor of using these tests instead of merging this. If they take too long to run, then we should select a small subset of these tests to run for every commit. If this is not possible for some reason, then we should have our own test and merge this.

[tnqn]

The K8s tests can be selected by focus and skip options which support regular expression, so doable if we only want to run a small subset of them. I didn't run them on Kind but I don't think there would be difference between home-grown tests and upstream tests for Kind.

[lzhecheng]

Let's use conformance's network policy testcases and antrea specific network policy testcases. I will close this PR now.

[antrea-bot]

Thanks for your PR.
Unit tests and code linters are run automatically every time the PR is updated.
E2e, conformance and network policy tests can only be triggered by a member of the vmware-tanzu organization. Regular contributors to the project should join the org.

The following commands are available:

• /test-e2e: to trigger e2e tests.
• /skip-e2e: to skip e2e tests.
• /test-conformance: to trigger conformance tests.
• /skip-conformance: to skip conformance tests.
• /test-networkpolicy: to trigger networkpolicy tests.
• /skip-networkpolicy: to skip networkpolicy tests.
• /test-all: to trigger all tests.
• /skip-all: to skip all tests.

These commands can only be run by members of the vmware-tanzu organization.