tiup: complete tiup cluster tls desc

[qiancai]

First-time contributors' checklist

• I've signed the Contributor License Agreement, which is required for the repository owners to accept my contribution.

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions (in Chinese).

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)

What is the related PR or file link(s)?

• This PR is translated from: tiup: complete tiup cluster tls desc docs-cn#21612
• Other reference link(s): cluster: support enable or disable TLS for an exiting cluster tiup#1657

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[github-actions]

Auto-sync completed successfully

Source PR: pingcap/docs-cn#21612
Target PR: #22861

English documentation has been updated based on Chinese documentation changes.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign icemap for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gemini-code-assist]

Code Review

This pull request adds a new file temp.md containing placeholder text. The review feedback indicates that the file lacks the required documentation structure, including a metadata block and an L1 heading, and suggests renaming the file to match the project's table of contents. A code suggestion was provided to implement the necessary structural changes.

I am having trouble creating individual review comments. Click here to see my feedback.

temp.md (1)

This file contains placeholder text and lacks the required documentation structure (metadata block and L1 heading). Additionally, the filename temp.md does not match the pull request title. Consider updating the correct file path /tiup/tiup-component-cluster-tls.md as referenced in TOC.md.

---
title: tiup cluster tls
summary: Complete description of the tiup cluster tls command.
---

# tiup cluster tls

References

1. Documentation files should follow the standard structure including metadata and proper heading hierarchy. ^(link)

[ti-chi-bot]

@xhebox: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

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.