[CONFORMANCE] Use kube-network-policies to run conformance tests in the CI

[tssurya]

Why this is needed:

We need to use https://github.com/kubernetes-sigs/kube-network-policies now that we have an implementation that will help us catch CI flakes and improve our testing framework

thanks @aojea for the awesome work here. Definitely helps having a non-vendor implementation based CI runs that we can play with and maintain

TODO: Add a CI lane for this

[aojea]

It is already merged, isn't it ?

#224

[astoycos]

I think @tssurya meant we should be running the core K8s network policy tests on the network-policy-api repo as well as in the core prow instance so that we can easily see if anything is broken/ go fix it

At the very least it'd be nice for us to be alerted if something was broken with the core tests so that we could assist in fixing them, since part of our charter is "maintaining the in-tree NetworkPolicy resource/tests"

[aojea]

you mean set a periodic job in prow?

[astoycos]

I was thinking run the core netpol tests against kube-network-policies in our github actions alongside the tests for ANP + BANP

But maybe Surya had something else in mind here?

[aojea]

kube-network-policies is used for kubernetes CI , periodic and presubmit

https://testgrid.k8s.io/sig-network-gce#network-policies,%20google-gce&width=20
https://testgrid.k8s.io/sig-network-gce#presubmit-network-policies,%20google-gce&width=20

There is a flake with one specific test , I'm investigating it here kubernetes-sigs/kube-network-policies#12, but it seems some kernel or OS thing

but there are zero flakes on the github actions in kube-network-policies

[aojea]

I don't fully understand but happy to help or discuss

[tssurya]

yes exactly what was done in #224 except I didn't see that PR :) Andrew merged it too quick haha
my plan was to use kube-network-policies for running e2e's tests in this repo for presubmits. (when we add new tests here in this repo or change some framework we don't have presubmits that tests the changes against PRs, that was my goal here)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.