Update scale-tidb-using-tiup.md

[easonn7]

First-time contributors' checklist

• [ ] I've signed Contributor License Agreement that's required for repo 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)
• [ ] v8.0 (TiDB 8.0 versions)
• [ ] v7.6 (TiDB 7.6 versions)
• [ ] v7.5 (TiDB 7.5 versions)
• [ ] v7.4 (TiDB 7.4 versions)
• [ ] v7.1 (TiDB 7.1 versions)
• [ ] v6.5 (TiDB 6.5 versions)
• [ ] v6.1 (TiDB 6.1 versions)
• [ ] v5.4 (TiDB 5.4 versions)
• [ ] v5.3 (TiDB 5.3 versions)
• [ ] v5.2 (TiDB 5.2 versions)
• [ ] v5.1 (TiDB 5.1 versions)
• [ ] v5.0 (TiDB 5.0 versions)

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

• This PR is translated from:
• Other reference link(s):

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

[ti-chi-bot[bot]]

Hi @easonn7. Thanks for your PR.

I'm waiting for a pingcap 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/test-infra repository.

[WalterWj]

@easonn7 Any update ?

[WalterWj]

Can this pr be merged as soon as possible?

[CLAassistant]

All committers have signed the CLA.

[lilin90]

/ok-to-test

[ti-chi-bot[bot]]

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

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/test-infra repository.

[ti-chi-bot[bot]]

[LGTM Timeline notifier]

Timeline:

• 2024-04-16 09:35:56.936021968 +0000 UTC m=+330776.047068415: :ballot_box_with_check: agreed by lilin90.
• 2024-04-16 09:36:17.767235915 +0000 UTC m=+330796.878282364: :ballot_box_with_check: agreed by qiancai.

[qiancai]

/approve

[ti-chi-bot[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

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

The pull request process is described here

Needs approval from an approver in each of these files:

• ~~OWNERS~~ [qiancai]

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

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #17135.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.6: #17136.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.0: #17137.