Expand `.Spec.Ingress` and `.Spec.Egress` tests for testing side-effects

kubernetes-sigs / network-policy-api

This repo addresses further work involving Kubernetes network security beyond the initial NetworkPolicy resource

Apache License 2.0

51 stars 29 forks source link

Open tssurya opened 1 year ago

tssurya commented 1 year ago

[ ] Currently the ingress-rules test focus on testing ingress traffic towards subject, even with these rules in place, we need to add a new test or two to those files to test egress from subject works fine since there are 0 egress rules in those files.
[ ] Currently the egress-rules test focus on testing egress traffic towards subject, even with these rules in place, we need to add a new test or two to those files to test ingress from subject works fine since there are 0 ingress rules in those files.

tssurya commented 1 year ago

/area conformance

k8s-triage-robot commented 6 months ago

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:

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

/lifecycle stale

tssurya commented 5 months ago

/remove-lifecycle stale

k8s-triage-robot commented 2 months ago

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:

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

/lifecycle stale

k8s-triage-robot commented 1 month ago

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:

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

/lifecycle rotten

astoycos commented 1 month ago

/remove-lifecycle rotten