CR

haim-kermany · haim-kermany · commit 5b7505392cba · 2024-07-08T14:52:01.000+03:00
diff --git a/pkg/ibmvpc/examples/out/explain_out/GroupingExternalSG1_all_vpcs_explain.txt b/pkg/ibmvpc/examples/out/explain_out/GroupingExternalSG1_all_vpcs_explain.txt
@@ -10,7 +10,7 @@ Path:
 
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from from vsi1-ky[10.240.10.4] to Public Internet 161.0.0.0-161.25.255.255,161.27.0.0-161.255.255.255;
+No connections from vsi1-ky[10.240.10.4] to Public Internet 161.0.0.0-161.25.255.255,161.27.0.0-161.255.255.255;
 connection is blocked by egress
 
 External traffic via PublicGateway: public-gw-ky
diff --git a/pkg/ibmvpc/examples/out/explain_out/GroupingExternalSG1_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/GroupingExternalSG1_all_vpcs_explain_debug.txt
@@ -20,7 +20,7 @@ Path is enabled; The relevant rules are:
 
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from from vsi1-ky[10.240.10.4] to Public Internet 161.0.0.0-161.25.255.255,161.27.0.0-161.255.255.255;
+No connections from vsi1-ky[10.240.10.4] to Public Internet 161.0.0.0-161.25.255.255,161.27.0.0-161.255.255.255;
 connection is blocked by egress
 
 External traffic via PublicGateway: public-gw-ky
diff --git a/pkg/ibmvpc/examples/out/explain_out/LBToResIPNode_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/LBToResIPNode_all_vpcs_explain_debug.txt
@@ -1,8 +1,8 @@
 Explaining connectivity from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca to 192.168.32.5 (iks-clusterid:1[192.168.32.5]) within ky-test-vpc
 =================================================================================================================================================
 
-No connections from from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LB private IP][192.168.36.6] to iks-clusterid:1[192.168.32.5];
-connection can not be initiated by Load Balancer
+No connections from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LB private IP][192.168.36.6] to iks-clusterid:1[192.168.32.5];
+connection will not be initiated by Load Balancer
 
 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
 Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-edge-acl allows connection
@@ -34,8 +34,8 @@ Path is disabled; The relevant rules are:
 
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LB private IP][192.168.40.6] to iks-clusterid:1[192.168.32.5];
-connection can not be initiated by Load Balancer
+No connections from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[LB private IP][192.168.40.6] to iks-clusterid:1[192.168.32.5];
+connection will not be initiated by Load Balancer
 
 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
 Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-edge-acl allows connection
@@ -67,8 +67,8 @@ Path is disabled; The relevant rules are:
 
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.0.0/22] to iks-clusterid:1[192.168.32.5];
-connection can not be initiated by Load Balancer
+No connections from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.0.0/22] to iks-clusterid:1[192.168.32.5];
+connection will not be initiated by Load Balancer
 
 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
 Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-private-2-others-acl allows connection
@@ -100,8 +100,8 @@ Path is disabled; The relevant rules are:
 
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.16.0/22] to iks-clusterid:1[192.168.32.5];
-connection can not be initiated by Load Balancer
+No connections from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.16.0/22] to iks-clusterid:1[192.168.32.5];
+connection will not be initiated by Load Balancer
 
 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
 Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-edge-acl allows connection
@@ -133,8 +133,8 @@ Path is disabled; The relevant rules are:
 
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.20.0/22] to iks-clusterid:1[192.168.32.5];
-connection can not be initiated by Load Balancer
+No connections from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.20.0/22] to iks-clusterid:1[192.168.32.5];
+connection will not be initiated by Load Balancer
 
 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
 Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-edge-acl allows connection
@@ -166,8 +166,8 @@ Path is disabled; The relevant rules are:
 
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.24.0/22] to iks-clusterid:1[192.168.32.5];
-connection can not be initiated by Load Balancer
+No connections from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.24.0/22] to iks-clusterid:1[192.168.32.5];
+connection will not be initiated by Load Balancer
 
 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
 Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-edge-acl allows connection
@@ -199,8 +199,8 @@ Path is disabled; The relevant rules are:
 
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from 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];
-connection can not be initiated by Load Balancer
+No connections 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];
+connection will not be initiated by Load Balancer
 
 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
 Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection
@@ -228,8 +228,8 @@ Path is disabled; The relevant rules are:
 
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.4.0/22] to iks-clusterid:1[192.168.32.5];
-connection can not be initiated by Load Balancer
+No connections from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.4.0/22] to iks-clusterid:1[192.168.32.5];
+connection will not be initiated by Load Balancer
 
 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
 Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-private-2-others-acl allows connection
@@ -261,8 +261,8 @@ Path is disabled; The relevant rules are:
 
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.8.0/22] to iks-clusterid:1[192.168.32.5];
-connection can not be initiated by Load Balancer
+No connections from kube-clusterid:1-8fdd1d0a2ce34deba99d0f885451b1ca[Potential LB private IP][192.168.8.0/22] to iks-clusterid:1[192.168.32.5];
+connection will not be initiated by Load Balancer
 
 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
 Egress: security group kube-r006-d7cfb31a-1d4b-40c8-83df-ce2e6f8f2e57 allows connection; network ACL ky-test-private-2-others-acl allows connection
diff --git a/pkg/ibmvpc/examples/out/explain_out/NACLExternal2_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/NACLExternal2_all_vpcs_explain_debug.txt
@@ -1,7 +1,7 @@
 Explaining connectivity from vsi1-ky to 100.128.0.0/32 within test-vpc1-ky
 ==========================================================================
 
-No connections from from vsi1-ky[10.240.10.4] to Public Internet 100.128.0.0/32;
+No connections from vsi1-ky[10.240.10.4] to Public Internet 100.128.0.0/32;
 connection is blocked by egress
 
 External traffic via PublicGateway: public-gw-ky
diff --git a/pkg/ibmvpc/examples/out/explain_out/NACLExternal3_all_vpcs_explain.txt b/pkg/ibmvpc/examples/out/explain_out/NACLExternal3_all_vpcs_explain.txt
@@ -1,7 +1,7 @@
 Explaining connectivity from 100.128.0.0/32 to vsi1-ky within test-vpc1-ky
 ==========================================================================
 
-No connections from from Public Internet 100.128.0.0/32 to vsi1-ky[10.240.10.4];
+No connections from Public Internet 100.128.0.0/32 to vsi1-ky[10.240.10.4];
 	There is no resource enabling inbound external connectivity
 ------------------------------------------------------------------------------------------------------------------------
 
diff --git a/pkg/ibmvpc/examples/out/explain_out/NACLGrouping_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/NACLGrouping_all_vpcs_explain_debug.txt
@@ -20,7 +20,7 @@ Path is enabled; The relevant rules are:
 
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from from vsi1-ky[10.240.10.4] to Public Internet 161.27.0.0/16;
+No connections from vsi1-ky[10.240.10.4] to Public Internet 161.27.0.0/16;
 connection is blocked by egress
 
 External traffic via PublicGateway: public-gw-ky
diff --git a/pkg/ibmvpc/examples/out/explain_out/NACLInternal3_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/NACLInternal3_all_vpcs_explain_debug.txt
@@ -1,7 +1,7 @@
 Explaining connectivity from vsi1-ky to vsi3a-ky within test-vpc1-ky
 ====================================================================
 
-No connections from from vsi1-ky[10.240.10.4] to vsi3a-ky[10.240.30.5];
+No connections from vsi1-ky[10.240.10.4] to vsi3a-ky[10.240.30.5];
 connection is blocked by egress
 
 Egress: security group sg1-ky allows connection; network ACL acl1-ky blocks connection
diff --git a/pkg/ibmvpc/examples/out/explain_out/NACLOnlyDenyNoConnQuery_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/NACLOnlyDenyNoConnQuery_all_vpcs_explain_debug.txt
@@ -1,7 +1,7 @@
 Explaining connectivity from vsi1-ky to vsi2-ky within test-vpc1-ky using "protocol: ICMP"
 ==========================================================================================
 
-No connections from from vsi1-ky[10.240.10.4] to vsi2-ky[10.240.20.4] using "protocol: ICMP";
+No connections from vsi1-ky[10.240.10.4] to vsi2-ky[10.240.20.4] using "protocol: ICMP";
 connection is blocked by egress
 
 Egress: security group sg1-ky allows connection; network ACL acl1-ky blocks connection
diff --git a/pkg/ibmvpc/examples/out/explain_out/NACLQueryConnection2_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/NACLQueryConnection2_all_vpcs_explain_debug.txt
@@ -1,7 +1,7 @@
 Explaining connectivity from vsi1-ky to 161.26.0.0/16 within test-vpc1-ky using "protocol: TCP"
 ===============================================================================================
 
-No connections from from vsi1-ky[10.240.10.4] to Public Internet 161.26.0.0/16 using "protocol: TCP";
+No connections from vsi1-ky[10.240.10.4] to Public Internet 161.26.0.0/16 using "protocol: TCP";
 connection is blocked by egress
 
 External traffic via PublicGateway: public-gw-ky
diff --git a/pkg/ibmvpc/examples/out/explain_out/QueryConnectionSGBasic4_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/QueryConnectionSGBasic4_all_vpcs_explain_debug.txt
@@ -20,7 +20,7 @@ Path is enabled; The relevant rules are:
 
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from from vsi1-ky[10.240.10.4] to Public Internet 161.16.0.0-161.25.255.255,161.27.0.0-161.31.255.255 using "protocol: UDP src-ports: 10-100 dst-ports: 443";
+No connections from vsi1-ky[10.240.10.4] to Public Internet 161.16.0.0-161.25.255.255,161.27.0.0-161.31.255.255 using "protocol: UDP src-ports: 10-100 dst-ports: 443";
 connection is blocked by egress
 
 External traffic via PublicGateway: public-gw-ky
diff --git a/pkg/ibmvpc/examples/out/explain_out/QueryConnectionSGBasic5_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/QueryConnectionSGBasic5_all_vpcs_explain_debug.txt
@@ -1,7 +1,7 @@
 Explaining connectivity from vsi1-ky to vsi3a-ky within test-vpc1-ky using "protocol: UDP src-ports: 10-100 dst-ports: 443"
 ===========================================================================================================================
 
-No connections from from vsi1-ky[10.240.10.4] to vsi3a-ky[10.240.30.5] using "protocol: UDP src-ports: 10-100 dst-ports: 443";
+No connections from vsi1-ky[10.240.10.4] to vsi3a-ky[10.240.30.5] using "protocol: UDP src-ports: 10-100 dst-ports: 443";
 connection is blocked both by ingress and egress
 
 Egress: security group sg1-ky blocks connection; network ACL acl1-ky allows connection
diff --git a/pkg/ibmvpc/examples/out/explain_out/SGInternal3SrcToExternalGroup_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/SGInternal3SrcToExternalGroup_all_vpcs_explain_debug.txt
@@ -1,15 +1,15 @@
 Explaining connectivity from 10.240.30.4/24 (vsi3a-ky[10.240.30.5], vsi3b-ky[10.240.30.4], db-endpoint-gateway-ky[10.240.30.6]) to 161.26.0.0/8 within test-vpc1-ky
 ===================================================================================================================================================================
 
-No connections from from db-endpoint-gateway-ky[10.240.30.6] to Public Internet 161.0.0.0/8;
+No connections from db-endpoint-gateway-ky[10.240.30.6] to Public Internet 161.0.0.0/8;
 	The dst is external but there is no Floating IP or Public Gateway connecting to public internet
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from from vsi3a-ky[10.240.30.5] to Public Internet 161.0.0.0/8;
+No connections from vsi3a-ky[10.240.30.5] to Public Internet 161.0.0.0/8;
 	The dst is external but there is no Floating IP or Public Gateway connecting to public internet
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from from vsi3b-ky[10.240.30.4] to Public Internet 161.0.0.0/8;
+No connections from vsi3b-ky[10.240.30.4] to Public Internet 161.0.0.0/8;
 	The dst is external but there is no Floating IP or Public Gateway connecting to public internet
 ------------------------------------------------------------------------------------------------------------------------
 
diff --git a/pkg/ibmvpc/examples/out/explain_out/SimpleExternalSG2_all_vpcs_explain.txt b/pkg/ibmvpc/examples/out/explain_out/SimpleExternalSG2_all_vpcs_explain.txt
@@ -1,7 +1,7 @@
 Explaining connectivity from 161.26.0.0/16 to vsi1-ky within test-vpc1-ky
 =========================================================================
 
-No connections from from Public Internet 161.26.0.0/16 to vsi1-ky[10.240.10.4];
+No connections from Public Internet 161.26.0.0/16 to vsi1-ky[10.240.10.4];
 	There is no resource enabling inbound external connectivity
 ------------------------------------------------------------------------------------------------------------------------
 
diff --git a/pkg/ibmvpc/examples/out/explain_out/SimpleExternalSG4_all_vpcs_explain.txt b/pkg/ibmvpc/examples/out/explain_out/SimpleExternalSG4_all_vpcs_explain.txt
@@ -1,7 +1,7 @@
 Explaining connectivity from vsi3b-ky to 161.26.0.0/32 within test-vpc1-ky
 ==========================================================================
 
-No connections from from vsi3b-ky[10.240.30.4] to Public Internet 161.26.0.0/32;
+No connections from vsi3b-ky[10.240.30.4] to Public Internet 161.26.0.0/32;
 	The dst is external but there is no Floating IP or Public Gateway connecting to public internet
 ------------------------------------------------------------------------------------------------------------------------
 
diff --git a/pkg/ibmvpc/examples/out/explain_out/VsiToVsi4_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/VsiToVsi4_all_vpcs_explain_debug.txt
@@ -1,7 +1,7 @@
 Explaining connectivity from 10.240.10.4 (vsi1-ky[10.240.10.4]) to 10.240.20.4 (vsi2-ky[10.240.20.4]) within test-vpc1-ky
 =========================================================================================================================
 
-No connections from from vsi1-ky[10.240.10.4] to vsi2-ky[10.240.20.4];
+No connections from vsi1-ky[10.240.10.4] to vsi2-ky[10.240.20.4];
 connection is blocked by egress
 
 Egress: security group sg1-ky blocks connection; network ACL acl1-ky allows connection
diff --git a/pkg/ibmvpc/examples/out/explain_out/VsiToVsi5_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/VsiToVsi5_all_vpcs_explain_debug.txt
@@ -1,7 +1,7 @@
 Explaining connectivity from vsi3a-ky to vsi2-ky within test-vpc1-ky
 ====================================================================
 
-No connections from from vsi3a-ky[10.240.30.5] to vsi2-ky[10.240.20.4];
+No connections from vsi3a-ky[10.240.30.5] to vsi2-ky[10.240.20.4];
 connection is blocked by ingress
 
 Egress: security group sg3-ky allows connection; network ACL acl3-ky allows connection
diff --git a/pkg/ibmvpc/examples/out/explain_out/multiNIsToSingleNI_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/multiNIsToSingleNI_all_vpcs_explain_debug.txt
@@ -34,7 +34,7 @@ TCP response is enabled; The relevant rules are:
 
 ------------------------------------------------------------------------------------------------------------------------
 
-No connections from from vsi3-ky[10.240.10.4] to vsi1-ky[10.240.10.5];
+No connections from vsi3-ky[10.240.10.4] to vsi1-ky[10.240.10.5];
 connection is blocked by egress
 
 Egress: security group sg1-ky blocks connection
diff --git a/pkg/ibmvpc/examples/out/explain_out/multiVPCNoCrossVPCRouter_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/multiVPCNoCrossVPCRouter_all_vpcs_explain_debug.txt
@@ -1,5 +1,5 @@
 Explaining connectivity from vsi1-ky to vsi31-ky
 ================================================
 
-No connections from from vsi1-ky to vsi31-ky;
+No connections from vsi1-ky to vsi31-ky;
 All connections will be blocked since source and destination are in different VPCs with no transit gateway to connect them
diff --git a/pkg/ibmvpc/examples/out/explain_out/multiVPCSameNamesCrossVPCByAddrNoTgw_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/multiVPCSameNamesCrossVPCByAddrNoTgw_all_vpcs_explain_debug.txt
@@ -1,5 +1,5 @@
 Explaining connectivity from 10.240.3.5 to 10.240.12.4
 ======================================================
 
-No connections from from 10.240.3.5 to 10.240.12.4;
+No connections from 10.240.3.5 to 10.240.12.4;
 All connections will be blocked since source and destination are in different VPCs with no transit gateway to connect them
diff --git a/pkg/ibmvpc/examples/out/explain_out/multiVPCSameNamesCrossVPCNoTgw_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/multiVPCSameNamesCrossVPCNoTgw_all_vpcs_explain_debug.txt
@@ -1,5 +1,5 @@
 Explaining connectivity from test-vpc0-ky/vsi1-ky to test-vpc1-ky/vsi1-ky
 =========================================================================
 
-No connections from from test-vpc0-ky/vsi1-ky to test-vpc1-ky/vsi1-ky;
+No connections from test-vpc0-ky/vsi1-ky to test-vpc1-ky/vsi1-ky;
 All connections will be blocked since source and destination are in different VPCs with no transit gateway to connect them
diff --git a/pkg/ibmvpc/examples/out/explain_out/multiVPCVsiToExternalMissingRouter_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/multiVPCVsiToExternalMissingRouter_all_vpcs_explain_debug.txt
@@ -1,7 +1,7 @@
 Explaining connectivity from vsi11-ky to 172.217.22.46/32 within test-vpc1-ky
 =============================================================================
 
-No connections from from vsi11-ky[10.240.11.4] to Public Internet 172.217.22.46/32;
+No connections from vsi11-ky[10.240.11.4] to Public Internet 172.217.22.46/32;
 	The dst is external but there is no Floating IP or Public Gateway connecting to public internet
 ------------------------------------------------------------------------------------------------------------------------
 
diff --git a/pkg/ibmvpc/examples/out/explain_out/tgwDisabledDenyPrefix_all_vpcs_explain.txt b/pkg/ibmvpc/examples/out/explain_out/tgwDisabledDenyPrefix_all_vpcs_explain.txt
@@ -1,7 +1,7 @@
 Explaining connectivity from ky-vsi1-subnet20 to ky-vsi0-subnet0
 ================================================================
 
-No connections from from test-vpc2-ky/ky-vsi1-subnet20[10.240.128.5] to test-vpc0-ky/ky-vsi0-subnet0[10.240.0.5];
+No connections from test-vpc2-ky/ky-vsi1-subnet20[10.240.128.5] to test-vpc0-ky/ky-vsi0-subnet0[10.240.0.5];
 All connections will be blocked since transit gateway denies route from source to destination
 
 Egress: security group sg21-ky allows connection; network ACL acl21-ky allows connection
diff --git a/pkg/ibmvpc/examples/out/explain_out/tgwDisabledDenyPrefix_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/tgwDisabledDenyPrefix_all_vpcs_explain_debug.txt
@@ -1,7 +1,7 @@
 Explaining connectivity from ky-vsi1-subnet20 to ky-vsi0-subnet0
 ================================================================
 
-No connections from from test-vpc2-ky/ky-vsi1-subnet20[10.240.128.5] to test-vpc0-ky/ky-vsi0-subnet0[10.240.0.5];
+No connections from test-vpc2-ky/ky-vsi1-subnet20[10.240.128.5] to test-vpc0-ky/ky-vsi0-subnet0[10.240.0.5];
 All connections will be blocked since transit gateway denies route from source to destination
 
 Egress: security group sg21-ky allows connection; network ACL acl21-ky allows connection
diff --git a/pkg/ibmvpc/examples/out/explain_out/tgwExampleCidr_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/tgwExampleCidr_all_vpcs_explain_debug.txt
diff --git a/pkg/ibmvpc/examples/out/explain_out/vpeToIksNodeNoProtocolConn_all_vpcs_explain_debug.txt b/pkg/ibmvpc/examples/out/explain_out/vpeToIksNodeNoProtocolConn_all_vpcs_explain_debug.txt
diff --git a/pkg/ibmvpc/explainability_test.go b/pkg/ibmvpc/explainability_test.go
