Add policy based routing test #4273
Conversation
|
@edwarnicke @zolug @tedlean |
Signed-off-by: Artem Glazychev <artem.glazychev@xored.com>
glazychev-art
changed the title
| data: | ||
| config.yaml: | | ||
| - from: 172.16.2.201/24 | ||
| proto: 6 |
There was a problem hiding this comment.
This field is super hard to understand. I think we should consider improving clarity.
| - proto: 17 | ||
| port: 6666 | ||
| - from: 2004::3/120 | ||
| proto: 17 |
There was a problem hiding this comment.
This field is super hard to understand. I think we should consider improving clarity.
| routes: | ||
| - prefix: 172.16.3.0/24 | ||
| nexthop: 172.16.2.200 | ||
| - proto: 17 |
There was a problem hiding this comment.
This field is super hard to understand. I think we should consider improving clarity.
There was a problem hiding this comment.
@glazychev-art Is it possible to replace proto: ${number} to something human readable?
|
OK, I see that protocol numbers are known https://en.wikipedia.org/wiki/List_of_IP_protocol_numbers So merging. @edwarnicke Let us know if you will have any questions or comments on this example. |
…ployments-k8s@main PR link: networkservicemesh/deployments-k8s#4273 Commit: 4b340c5 Author: Network Service Mesh Bot Date: 2022-01-25 01:05:35 -0600 Message: - Update go.mod and go.sum to latest version from networkservicemesh/de… Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Issue: networkservicemesh/api#119
Signed-off-by: Artem Glazychev artem.glazychev@xored.com