Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

Hi @huntsman-li. 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.

@googlebot I signed it!

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

/ok-to-test

/review

Headers with anchors lint failed. Can you help us to fix these errors? @geeknoid

430 files are free from spelling errors
./zh/docs/concepts/security/index.md
79 | ### Istio 安全与 SPIFFE{#istio-security-vs-spiffe}
91 | ## PKI{#pki}
100 | ### Kubernetes 方案{#kubernetes-scenario}
122 | ### Kubernetes 中的代理节点{#node-agent-in-kubernetes}
227 | ### 双向 TLS 认证{#mutual-tls-authentication}
460 | #### ServiceRole{#servicerole}
538 | #### ServiceRoleBinding{#servicerolebinding}
602 | ### 在普通 TCP 协议上使用 Istio 认证{#using-istio-authorization-on-plain-tcp-protocols}
8 spelling errors found in 429 files
To learn how to address spelling errors, please see https://istio.io/about/contribute/creating-and-editing-pages/#linting
Running ["LinkCheck", "HtmlCheck", "OpenGraphCheck", "ImageCheck", "ScriptCheck"] on ["./public"] on *.html...

I guess the spell checker treats the fragment name as normal text and insists it be valid. So to fix this, you need to use words from the dictionary:

• kubernetes should be Kubernetes
• servicerole should be service-role
• servicerolebinding should be service-role-binding
• tcp -> TCP
• tls -> TLS