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
KEP 1441 - kubectl debug #1441
Comments
/stage alpha |
Hey there @soltysh can you confirm that this will be in the 1.18 release? To make it into the release, the KEP will need to be merged as |
@jeremyrickard yup, I confirm. The KEP should be merged later today after SIG-CLI call, then we'll start with the implementation right away. |
Thanks for getting the KEP in @soltysh |
Updated the issue description with KEP link. |
Hello, @soltysh, I'm 1.18 docs lead. |
@VineethReddy02 ack, this will include doc updates and we will open a placeholder PR by Feb 28. Thanks! |
@helayoty I expect this to merge in time. |
Add support for override image command & args for debug some error between container starting? kubectl run nginx --image nginx --debug
apiVersion: apps/v1
kind: Deployment
metadata:
creationTimestamp: null
labels:
run: nginx
name: nginx
spec:
replicas: 1
selector:
matchLabels:
run: nginx
strategy: {}
template:
metadata:
creationTimestamp: null
labels:
run: nginx
spec:
containers:
- image: nginx
name: nginx
command: ["sleep"]
args: ["1d"]
resources: {} |
@cnk8s This is indeed included in the proposal. See Pod Troubleshooting by Copy |
@aylei Are you interested in working on Pod Troubleshooting by Copy for 1.19? or anything else related to debug? |
@verb Absolutely |
I will draft a PR this week |
@verb reading the KEP, I still don't get how pod-troubleshooting by copy would work, what does copy mean in this case? |
@chrisnegus |
Hi @verb 1.24 Enhancements Team here, (Update) |
Hey y'all! We're approaching last call for feature blogs, as the freeze is Wednesday, March 23. If you would like to have a feature blog for this, please add it to the tracking sheet and reach out to me if you have any questions. Thank you! |
Hi @gracenng, We didn't get this finished in time. Let's please slip this to 1.25. Thanks! |
Hi @parul5sahoo @soltysh We're going to be working on this in the 1.25 cycle, but it will not be graduating. Do we need to add it to the v1.25 milestone? Thanks! |
Given that we're not going to promote this, but rather still keep it as beta I don't see a reason for update to the KEP. |
@verb, from issue kubernetes/kubernetes#110126, I realized the suggested way to "bypassing security policy" is done by "usernames" configured by "exemptions". |
It looks like this feature moved to beta in v1.22 with docs apparently missing (see kubernetes/website#32265) SIG CLI folks, please consider adding a good level of docs coverage before this graduates to stable. |
@verb can you make sure this is addressed? |
@sftim @soltysh The PR you linked (kubernetes/website#32265) is for 1.24, but we didn't end up merging any changes in 1.24 so I let the PR expire.
I'm motivated to write docs, but it's hard for me to know what SIG Docs considers a good level of coverage. I'm happy to add items to the graduation criteria if you have guidance for deliverables (e.g. add a new troubleshooting doc, split the existing pod troubleshooting doc) otherwise I'll try to figure it out when the time comes and reach out if it's non-trivial. |
kubernetes/website#35031 is the main piece that I think is missing. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". 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. |
Let's reopen this since development has picked up again. I think we should finish implementing debug profiles, mark kubectl debug as stable and then improve it with future KEPs. wdyt @ardaguclu? /reopen |
@verb: Reopened this issue. 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. |
Enhancement Description
The text was updated successfully, but these errors were encountered: