Skip to content

Commit 5f8817d

Browse files
haim-kermanyhaim-kermany
committed
english
1 parent b64b3d7 commit 5f8817d

File tree

3 files changed

+29
-29
lines changed

3 files changed

+29
-29
lines changed

‎pkg/ibmvpc/examples/out/explain_out/LBToIksNode_all_vpcs_explain_debug.txt

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Details:
1212
~~~~~~~~
1313
Path is enabled; The relevant rules are:
1414
Load Balancer:
15-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] allows connection to iks-node[192.168.4.4] which is one of its pool members
15+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] may initiate a connection to iks-node[192.168.4.4], which is one of its pool members
1616

1717
Egress:
1818
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -53,7 +53,7 @@ Details:
5353
~~~~~~~~
5454
Path is enabled; The relevant rules are:
5555
Load Balancer:
56-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] allows connection to iks-node[192.168.4.4] which is one of its pool members
56+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] may initiate a connection to iks-node[192.168.4.4], which is one of its pool members
5757

5858
Egress:
5959
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -94,7 +94,7 @@ Details:
9494
~~~~~~~~
9595
Path is enabled; The relevant rules are:
9696
Load Balancer:
97-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] allows connection to iks-node[192.168.4.4] which is one of its pool members
97+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] may initiate a connection to iks-node[192.168.4.4], which is one of its pool members
9898

9999
Egress:
100100
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -135,7 +135,7 @@ Details:
135135
~~~~~~~~
136136
Path is enabled; The relevant rules are:
137137
Load Balancer:
138-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] allows connection to iks-node[192.168.4.4] which is one of its pool members
138+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] may initiate a connection to iks-node[192.168.4.4], which is one of its pool members
139139

140140
Egress:
141141
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -176,7 +176,7 @@ Details:
176176
~~~~~~~~
177177
Path is enabled; The relevant rules are:
178178
Load Balancer:
179-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] allows connection to iks-node[192.168.4.4] which is one of its pool members
179+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] may initiate a connection to iks-node[192.168.4.4], which is one of its pool members
180180

181181
Egress:
182182
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -217,7 +217,7 @@ Details:
217217
~~~~~~~~
218218
Path is enabled; The relevant rules are:
219219
Load Balancer:
220-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] allows connection to iks-node[192.168.4.4] which is one of its pool members
220+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] may initiate a connection to iks-node[192.168.4.4], which is one of its pool members
221221

222222
Egress:
223223
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -258,7 +258,7 @@ Details:
258258
~~~~~~~~
259259
Path is enabled; The relevant rules are:
260260
Load Balancer:
261-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] allows connection to iks-node[192.168.4.4] which is one of its pool members
261+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] may initiate a connection to iks-node[192.168.4.4], which is one of its pool members
262262

263263
Egress:
264264
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -299,7 +299,7 @@ Details:
299299
~~~~~~~~
300300
Path is enabled; The relevant rules are:
301301
Load Balancer:
302-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] allows connection to iks-node[192.168.4.4] which is one of its pool members
302+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] may initiate a connection to iks-node[192.168.4.4], which is one of its pool members
303303

304304
Egress:
305305
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -327,7 +327,7 @@ Details:
327327
~~~~~~~~
328328
Path is enabled; The relevant rules are:
329329
Load Balancer:
330-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] allows connection to iks-node[192.168.4.4] which is one of its pool members
330+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] may initiate a connection to iks-node[192.168.4.4], which is one of its pool members
331331

332332
Egress:
333333
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules

‎pkg/ibmvpc/examples/out/explain_out/LBToResIPNode_all_vpcs_explain_debug.txt

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Explaining connectivity from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca t
44
No connections are allowed from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LB private IP][192.168.36.6] to iks-clusterid:1[192.168.32.5];
55
connection is blocked by Load Balancer
66

7-
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
7+
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
88
Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-edge-acl allows connection
99
Ingress: network ACL ky-test-edge-acl allows connection; security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection
1010

@@ -16,7 +16,7 @@ Details:
1616
~~~~~~~~
1717
Path is disabled; The relevant rules are:
1818
Load Balancer:
19-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
19+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
2020

2121
Egress:
2222
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -37,7 +37,7 @@ Path is disabled; The relevant rules are:
3737
No connections are allowed from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LB private IP][192.168.40.6] to iks-clusterid:1[192.168.32.5];
3838
connection is blocked by Load Balancer
3939

40-
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
40+
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
4141
Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-edge-acl allows connection
4242
Ingress: network ACL ky-test-edge-acl allows connection; security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection
4343

@@ -49,7 +49,7 @@ Details:
4949
~~~~~~~~
5050
Path is disabled; The relevant rules are:
5151
Load Balancer:
52-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
52+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
5353

5454
Egress:
5555
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -70,7 +70,7 @@ Path is disabled; The relevant rules are:
7070
No connections are allowed from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.0.0/22] to iks-clusterid:1[192.168.32.5];
7171
connection is blocked by Load Balancer
7272

73-
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
73+
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
7474
Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-private-2-others-acl allows connection
7575
Ingress: network ACL ky-test-edge-acl allows connection; security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection
7676

@@ -82,7 +82,7 @@ Details:
8282
~~~~~~~~
8383
Path is disabled; The relevant rules are:
8484
Load Balancer:
85-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
85+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
8686

8787
Egress:
8888
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -103,7 +103,7 @@ Path is disabled; The relevant rules are:
103103
No connections are allowed from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.16.0/22] to iks-clusterid:1[192.168.32.5];
104104
connection is blocked by Load Balancer
105105

106-
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
106+
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
107107
Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-edge-acl allows connection
108108
Ingress: network ACL ky-test-edge-acl allows connection; security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection
109109

@@ -115,7 +115,7 @@ Details:
115115
~~~~~~~~
116116
Path is disabled; The relevant rules are:
117117
Load Balancer:
118-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
118+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
119119

120120
Egress:
121121
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -136,7 +136,7 @@ Path is disabled; The relevant rules are:
136136
No connections are allowed from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.20.0/22] to iks-clusterid:1[192.168.32.5];
137137
connection is blocked by Load Balancer
138138

139-
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
139+
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
140140
Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-edge-acl allows connection
141141
Ingress: network ACL ky-test-edge-acl allows connection; security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection
142142

@@ -148,7 +148,7 @@ Details:
148148
~~~~~~~~
149149
Path is disabled; The relevant rules are:
150150
Load Balancer:
151-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
151+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
152152

153153
Egress:
154154
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -169,7 +169,7 @@ Path is disabled; The relevant rules are:
169169
No connections are allowed from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.24.0/22] to iks-clusterid:1[192.168.32.5];
170170
connection is blocked by Load Balancer
171171

172-
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
172+
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
173173
Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-edge-acl allows connection
174174
Ingress: network ACL ky-test-edge-acl allows connection; security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection
175175

@@ -181,7 +181,7 @@ Details:
181181
~~~~~~~~
182182
Path is disabled; The relevant rules are:
183183
Load Balancer:
184-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
184+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
185185

186186
Egress:
187187
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -202,7 +202,7 @@ Path is disabled; The relevant rules are:
202202
No connections are allowed from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.32.0-192.168.32.4,192.168.32.6-192.168.35.255] to iks-clusterid:1[192.168.32.5];
203203
connection is blocked by Load Balancer
204204

205-
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
205+
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
206206
Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection
207207
Ingress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection
208208

@@ -214,7 +214,7 @@ Details:
214214
~~~~~~~~
215215
Path is disabled; The relevant rules are:
216216
Load Balancer:
217-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
217+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
218218

219219
Egress:
220220
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -231,7 +231,7 @@ Path is disabled; The relevant rules are:
231231
No connections are allowed from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.4.0/22] to iks-clusterid:1[192.168.32.5];
232232
connection is blocked by Load Balancer
233233

234-
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
234+
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
235235
Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-private-2-others-acl allows connection
236236
Ingress: network ACL ky-test-edge-acl allows connection; security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection
237237

@@ -243,7 +243,7 @@ Details:
243243
~~~~~~~~
244244
Path is disabled; The relevant rules are:
245245
Load Balancer:
246-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
246+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
247247

248248
Egress:
249249
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules
@@ -264,7 +264,7 @@ Path is disabled; The relevant rules are:
264264
No connections are allowed from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.8.0/22] to iks-clusterid:1[192.168.32.5];
265265
connection is blocked by Load Balancer
266266

267-
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
267+
Load Balancer: kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
268268
Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-private-2-others-acl allows connection
269269
Ingress: network ACL ky-test-edge-acl allows connection; security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection
270270

@@ -276,7 +276,7 @@ Details:
276276
~~~~~~~~
277277
Path is disabled; The relevant rules are:
278278
Load Balancer:
279-
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] blocks connection to iks-clusterid:1[192.168.32.5] which is not one of its pool members
279+
kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LoadBalancer] will not connect to iks-clusterid:1[192.168.32.5], since it is not its pool member
280280

281281
Egress:
282282
security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection with the following allow rules

‎pkg/ibmvpc/vpc.go

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -348,10 +348,10 @@ func (lbr *LoadBalancerRule) Deny() bool { return lbr.deny }
348348

349349
func (lbr *LoadBalancerRule) String() string {
350350
if lbr.Deny() {
351-
return fmt.Sprintf("%s blocks connection to %s which is not one of its pool members\n",
351+
return fmt.Sprintf("%s will not connect to %s, since it is not its pool member\n",
352352
lbr.lb.nameWithKind(), lbr.dst.Name())
353353
}
354-
return fmt.Sprintf("%s allows connection to %s which is one of its pool members\n",
354+
return fmt.Sprintf("%s may initiate a connection to %s, which is one of its pool members\n",
355355
lbr.lb.nameWithKind(), lbr.dst.Name())
356356
}
357357

0 commit comments

Comments
 (0)