diff options
| -rw-r--r-- | demo/sfc-setup/README.md | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/demo/sfc-setup/README.md b/demo/sfc-setup/README.md index d2afd73..676fa88 100644 --- a/demo/sfc-setup/README.md +++ b/demo/sfc-setup/README.md @@ -92,18 +92,35 @@ Deploy the SFC as following $ kubectl apply -f demo/sfc-setup/deploy/slb-ngfw-sdewan-cnf-deployment.yaml $ kubectl apply -f demo/sfc-setup/deploy/ms1.yaml ``` +## Test Scenario - to comprehend multiple deployment variations + + +This show the test scenario we created in this demo. + Pinging for goole.com or curl example.com should fail in both ms1 and TM1 ``` $ kubectl apply -f demo/sfc-setup/deploy/sfc.yaml ``` Pinging for google.com or curl example.com should be successful in both ms1 and TM1 +## Traffic from external entities with sfc + + +## Traffic from pod within the cluster with sfc + + Let try to apply icmp reject rule in SDEWAN cnf ``` $ kubectl apply -f demo/sfc-setup/deploy/firewall-dyn-net-2.yaml $ kubectl apply -f demo/sfc-setup/deploy/firewall-right-pnetwork.yaml $ kubectl apply -f demo/sfc-setup/deploy/firewall-rule-reject-icmp-right-pnetwork.yaml ``` +## Traffic from external entities with sfc - SDEWAN icmp reject + + +## Traffic from pod within the cluster with sfc - SDEWAN icmp reject + + Pinging for google.com will fail and curl example.com should be successful in both ms1 and TM1 ## License |