Skip to content
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

tidb-in-kubernetes: add doc to restart tidb components on k8s (#1759) #1938

Merged
merged 1 commit into from
Mar 4, 2020

Conversation

sre-bot
Copy link
Contributor

@sre-bot sre-bot commented Mar 4, 2020

cherry-pick #1759 to release-3.1


What is changed, added or deleted?

Add a document to restart TiDB components on Kubernetes.

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

pingcap/docs-cn#2156

Which version does your change affect?

dev, v3.0, v3.1

…p#1759)

* tidb-in-kubernetes: add doc to restart tidb components on k8s

* address comments

* tidb-in-kubernetes: refine format

* make the same changes as before

* address comments from lilian

* address comment on wording

Co-authored-by: Keke Yi <40977455+yikeke@users.noreply.github.com>
Co-authored-by: Lilian Lee <lilin@pingcap.com>
Co-authored-by: DanielZhangQD <36026334+DanielZhangQD@users.noreply.github.com>
@sre-bot sre-bot added area/tidb-in-k8s-v1.0 translation/from-docs-cn This PR is translated from a PR in pingcap/docs-cn. type/cherry-pick-for-release-3.1 This PR is cherry-picked to release-3.1 from a source PR. labels Mar 4, 2020
Copy link
Member

@lilin90 lilin90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lilin90 lilin90 merged commit a3eb80e into pingcap:release-3.1 Mar 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tidb-in-k8s-v1.0 translation/from-docs-cn This PR is translated from a PR in pingcap/docs-cn. type/cherry-pick-for-release-3.1 This PR is cherry-picked to release-3.1 from a source PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants