pingcap / pingcap/docs-tidb-operator
replace tkctl with kubectl command line
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 52
- Forks
- 129
- Avg merge
- 12m
- Merged PRs (30d)
- 2
Description
File: /release-1.4/zh/network-issues.md
在 https://docs.pingcap.com/zh/tidb-in-kubernetes/stable/use-tkctl 说到：
注意
PingCAP 从 v1.1.x 开始不再维护 tkctl，以下部分功能可能不可用，请直接使用对应的 kubectl 命令。
这里应该换成 kubectl 相应的命令。而且 tkctl 不工作
$ tkctl debug -n tidb-cluster basic-monitor-0
Defaulting container name to prometheus.
waiting for pod debug-launcher-da7c45c1-819b-4bdd-99a7-53ffac6ebc5b running...
error: pod ran to completion
这个报错是在 AKS 下
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with release-1.4/zh/network-issues.md and the linked use-tkctl documentation page. Review the tkctl example and identify the corresponding kubectl commands, using the reported AKS failure as context. Done means the affected Chinese documentation no longer directs users to tkctl and shows usable kubectl guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100