pingcap / pingcap/tidb-operator
tkctl support for containerd based K8s setup
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
tkctl tool does not work in K8s+containerd setup.
tkctl debug basic-pd-0 --image=pingcap/tidb-debug:latest --launcher-image=pingcap/debug-launcher:latest --docker-socketl=/var/run/containerd/containerd.sock
Error:
F1203 14:51:23.617165 74503 helpers.go:114] error: pod ran to completion
This functionality will be much required going forward: K8s Dockershim Deprecation
Contributor guide
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
The issue centers on the tkctl debug command and its --docker-socketl argument; start by tracing that command and reproducing the failure in a Kubernetes setup using containerd. Done means the shown debug invocation works with the containerd socket instead of ending with “pod ran to completion.” No file or test is named, so locate relevant coverage before changing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100