docs: fix command execution issue and tcpdump port error in task mtls-migration

[kibaamor]

Two issues in task mtls/migration(Mutual TLS Migration/双向 TLS 迁移):

1. Some commands will fail if executed in the zsh shell.
2. Tcpdump port should be 8080 instead of 80.

Description

1. All commands for testing sending requests between namespaces will fail if it was executed in the zsh shell.

$ for from in "foo" "bar" "legacy"; do for to in "foo" "bar"; do kubectl exec "$(kubectl get pod -l app=sleep -n ${from} -o jsonpath={.items..metadata.name})" -c sleep -n ${from} -- curl http://httpbin.${to}:8000/ip -s -o /dev/null -w "sleep.${from} to httpbin.${to}: %{http_code}\n"; done; done
sleep.foo to httpbin.foo: 000
command terminated with exit code 3
sleep.foo to httpbin.bar: 000
command terminated with exit code 3
sleep.bar to httpbin.foo: 000
command terminated with exit code 3
sleep.bar to httpbin.bar: 000
command terminated with exit code 3
sleep.legacy to httpbin.foo: 000
command terminated with exit code 3
sleep.legacy to httpbin.bar: 000
command terminated with exit code 3

Like in task Authentication Policy, I suggest that the test URLs should be enclosed in double quotes.

- ... curl http://httpbin.${to}:8000/ip -s ...
+ ... curl "http://httpbin.${to}:8000/ip" -s ...

2. The tcpdump listening port should be 8080 instead of 80, because httpbin container is listening port 8080.

$ cat samples/httpbin/httpbin.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: httpbin
spec:
  template:
    spec:
      containers:
      - image: docker.io/kong/httpbin
        name: httpbin
        ports:
        - containerPort: 8080
...

Based on the description above, I created this PR to fix these issues in both the English and Chinese documents.
Please take a look.
Thanks.

Reviewers

• Ambient
• Docs
• Installation
• Networking
• Performance and Scalability
• Extensions and Telemetry
• Security
• Test and Release
• User Experience
• Developer Infrastructure
• Localization/Translation

• Mutual TLS Migration
• 双向 TLS 迁移

[istio-testing]

Hi @kibaamor. Thanks for your PR.

I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[dhawton]

/ok-to-test