aylei / aylei/kubectl-debug

kubectl debug状态为CrashLoopBackOff的Pod报错

Open
#40 8 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
2.3k
Forks
303
PR merge metrics
No merged PRs in 30d

Description

[root@sz-5-centos163 src]# kubectl debug finance-payment-kingdee-realname-cgi--test5-6f46ff966c-rm6dl -n finance --fork

error parsing configuration file: yaml: line 36: found unexpected end of streamWaiting for pod finance-payment-kingdee-realname-cgi--test5-6f46ff966c-rm6dl-067b70f9-9197-11e9-8494-00163e340364-debug to run...
Error occurred while waiting for pod to run: pod ran to completion
error: pod ran to completion

但是查看debug-agent pod已经是running。
请问这个是什么情况?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the reported kubectl debug command and inspect the debug-agent pod status and logs. Compare the command's completion handling with the observed running agent, then determine why the YAML parsing and pod-completion errors occur. The repository notes that it is no longer maintained, so check the linked replacement project before pursuing a fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
cli, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.