[ENHANCEMENT] Add Northbound traffic support for ANP API

[tssurya]

Is your enhancement request related to a problem? Please describe. This is follow of up of https://github.com/kubernetes-sigs/network-policy-api/issues/28 This issue tracks adding support for northbound traffic use case and also host-networked pod traffic use case for ANP from CNI pods.

Describe the solution you'd like https://github.com/kubernetes-sigs/network-policy-api/pull/117 outlines the details, it has undergone some rounds of review already at https://github.com/kubernetes-sigs/network-policy-api/pull/86

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

### Tasks
- [ ] https://github.com/kubernetes-sigs/network-policy-api/pull/117
- [ ] https://github.com/kubernetes-sigs/network-policy-api/pull/143
- [ ] Document egress samples
- [ ] https://github.com/kubernetes-sigs/network-policy-api/pull/144
- [ ] https://github.com/kubernetes-sigs/network-policy-api/pull/185
- [ ] https://github.com/kubernetes-sigs/network-policy-api/pull/193

[tssurya]

/assign @tssurya

[tssurya]

Now that the Provisional NPEP is done, I am working on PoC to implement it and then will re-open the NPEP in the implementable phase with link to PoC.

[tssurya]

/label kind/feature

[k8s-ci-robot]

@tssurya: The label(s) /label kind/feature cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to [this](https://github.com/kubernetes-sigs/network-policy-api/issues/126#issuecomment-1732597176): >/label kind/feature Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[tssurya]

/kind feature

[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

[astoycos]

/remove-lifecycle stale

[tssurya]

Status:

1. All design phase NPEPs have merged
2. NodeSelector peer API change has merged
3. inline CIDR selector API change PR is under progress
4. Starting on conformance tests for nodeselector

[tssurya]

Status:

1. All design phase NPEPs have merged
2. NodeSelector peer API change has merged
3. inline CIDR selector API change PR is merged
4. nodeSelector conformance test PR is waiting for reviews
5. starting on cidr conformance tests

[tssurya]

This task is done, closing it!