-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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? |
Have you considered adding support for |
@alculquicondor this will be handled by this KEP #4293. I opened this #4408 to mark |
/label lead-opted-in |
Hello @verb, @ardaguclu, @soltysh 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024. This enhancement is targeting for stage Here's where this enhancement currently stands:
The status of this enhancement is marked as |
I think, we can close this issue as completed. |
👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating. To opt in, you need to open a Feature Blog placeholder PR against the website repository. |
Hey, @verb and @soltysh 👋, v1.30 Docs Shadow here. Does this enhancement work planned for v1.30 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, February 22nd, 2024 18:00 PDT Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!
Based on Slack discussion, marking this as |
Hello again @verb, @ardaguclu, @soltysh 👋, Enhancements team here. Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 . Here's where this enhancement currently stands:
For this enhancement, it looks like the KEPs status on Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
Hello @verb, @ardaguclu, @soltysh 👋 Enhancements team here, Unfortunately, the implementation (code related) PR(s) associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the If you still wish to progress this enhancement in /milestone clear |
We have promoted this to GA and can close this issue as completed; |
@ardaguclu: Closing 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
k/enhancements
) update PR(s): Promote kubectl debug to GA #4408k/k
) update PR(s):k/website
) update(s):The text was updated successfully, but these errors were encountered: