forked from IBM/network-config-analyzer
-
Notifications
You must be signed in to change notification settings - Fork 0
/
testcase1-scheme.yaml
95 lines (85 loc) · 1.88 KB
/
testcase1-scheme.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
namespaceList: ../../example_podlist/ns_list.json
podList: ../../example_podlist/pods_list.json
networkConfigList:
- name: np1
networkPolicyList:
- testcase1-networkpolicy1.yaml
expectedWarnings: 0
- name: np2
networkPolicyList:
- testcase1-networkpolicy2.yaml
expectedWarnings: 0
- name: np3 # testing json policy from file entry
networkPolicyList:
- testcase1-networkpolicy1.json
expectedWarnings: 0
- name: notPolicyFile
networkPolicyList:
- testcase1-readme.yaml
queries:
- name: connectivity_map
connectivityMap:
- np1
- np2
expected: 0
outputConfiguration:
outputFormat: dot
fwRulesRunInTestMode: false
- name: sanity
sanity:
- np1
expected: 1
- name: sanity_json_np
sanity:
- np3
expected: 1
- name: compare_np1_and_np2
twoWayContainment:
- np1
- np2
expected: 3
- name: np1_and_np2_are_not_strongly_equivalent
strongEquivalence:
- np1
- np2
expected: 1
- name: np1_and_np1_are_strongly_equivalent
strongEquivalence:
- np1
- np1
expected: 0
- name: compare_specific_policies_in_np1_and_np2
equivalence:
- np1/default/allow-egress-deny-ingress-within-namespace
- np2/default/allow-ingress-deny-egress-within-namespace
- np1/default/allow-agent-to-analyzer-via-ingress
expected: 2
- name: redundancy_np1_and_np2
redundancy:
- np1
- np2
expected: 2
- name: pairwiseInterferes_np1_and_np2
pairwiseInterferes:
- np1
- np2
expected: 0
- name: not_empty
emptiness:
- np1
- np2
expected: 0
- name: not_vacuous
vacuity:
- np1
- np2
- name: containment_np1_and_np2
containment:
- np1
- np2
expected: 1
- name: containment_np2_and_np1
containment:
- np2
- np1
expected: 1