-
Notifications
You must be signed in to change notification settings - Fork 656
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document pre/post upgrade and reload scripts #17611
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rest LGTM
- Run a script before the reload. | ||
- Data type: `STRINGS` | ||
- This option specifies the path of the command that will be ran on the host that is to be reloaded. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Run a script before the reload. | |
- Data type: `STRINGS` | |
- This option specifies the path of the command that will be ran on the host that is to be reloaded. | |
- Runs a script before the reload. | |
- Data type: `STRINGS` | |
- This option specifies the path of a script to be run on the host that is to be reloaded. |
- Run a script after the reload. | ||
- Data type: `STRINGS` | ||
- This option specifies the path of the command that will be ran on the host that was reloaded. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Run a script after the reload. | |
- Data type: `STRINGS` | |
- This option specifies the path of the command that will be ran on the host that was reloaded. | |
- Runs a script after the reload. | |
- Data type: `STRINGS` | |
- This option specifies the path of a script to be run after the reload of a host. |
- Run a script before the upgrade. | ||
- Data type: `STRINGS` | ||
- This option specifies the path of the command that will be ran on the host that is to be upgraded. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Run a script before the upgrade. | |
- Data type: `STRINGS` | |
- This option specifies the path of the command that will be ran on the host that is to be upgraded. | |
- Runs a script before the upgrade. | |
- Data type: `STRINGS` | |
- This option specifies the path of a script to be run on the host that is to be upgraded. |
- Run a script after the upgrade. | ||
- Data type: `STRINGS` | ||
- This option specifies the path of the command that will be ran after the upgrade of a host. This command will be executed on the upgraded host itself. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Run a script after the upgrade. | |
- Data type: `STRINGS` | |
- This option specifies the path of the command that will be ran after the upgrade of a host. This command will be executed on the upgraded host itself. | |
- Runs a script after the upgrade. | |
- Data type: `STRINGS` | |
- This option specifies the path of a script to be run after the upgrade of a host. This command will be executed on the upgraded host itself. |
[LGTM Timeline notifier]Timeline:
|
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.
What is the related PR or file link(s)?
pingcap/tiup#2130
Do your changes match any of the following descriptions?