[ICN-213] OpenNESS gap for Network Policy Created: 11/Dec/19 Updated: 16/Jul/20 Resolved: 09/Jan/20 |
|
| Status: | Done |
| Project: | Integrated Cloud Native NFV |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | High |
| Reporter: | Huifeng Le | Assignee: | Chenjie Xu |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | OpenNESS integration in ICN |
| Description |
|
Investigate Network Policy Gap for OpenNESS integration |
| Comments |
| Comment by Chenjie Xu [ 17/Jan/20 ] |
|
The gap analysis has been added to the Akraino ICN OpenNESS wiki page as following: |
| Comment by Chenjie Xu [ 09/Jan/20 ] |
|
1. To deploy a Network Policy allowing ingress traffic on port 5000 (tcp and udp) from 192.168.1.0/24 network to OpenVINO consumer application pod, create the following specification file for this Network Policy: apiVersion: networking.k8s.io/v1 2. Create the Network Policy: |
| Comment by Chenjie Xu [ 09/Jan/20 ] |
|
By default, in a Network Edge environment, all ingress traffic is blocked (services running inside of deployed applications are not reachable) and all egress traffic is enabled (pods are able to reach the internet). The following NetworkPolicy definition is used: apiVersion: networking.k8s.io/v1 |