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
Better understanding of kubectl attach description #90959
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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. I understand the commands that are listed here. |
Welcome @ica10888! |
Hi @ica10888. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/check-cla |
/ok-to-test |
/test pull-kubernetes-e2e-gce-100-performance |
Thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: apelisse, ica10888 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thanks |
/test pull-kubernetes-e2e-gce-ubuntu-containerd |
/test all |
/retest Review the full test history for this PR. Silence the bot with an |
3 similar comments
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
/retest Review the full test history for this PR. Silence the bot with an |
1 similar comment
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
2 similar comments
/retest |
/retest |
/retest Review the full test history for this PR. Silence the bot with an |
2 similar comments
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
/retest
…On Sun, Jul 12, 2020 at 8:40 PM Kubernetes Prow Robot < ***@***.***> wrote:
@ica10888 <https://github.com/ica10888>: The following test *failed*, say
/retest to rerun all failed tests:
Test name Commit Details Rerun command
pull-kubernetes-e2e-kind 4fc4eb0
<4fc4eb0>
link
<https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/90959/pull-kubernetes-e2e-kind/1282314417639264257> /test
pull-kubernetes-e2e-kind
Full PR test history
<https://prow.k8s.io/pr-history?org=kubernetes&repo=kubernetes&pr=90959>. Your
PR dashboard. Please help us cut down on flakes by linking to
<https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/kubernetes/kubernetes/issues?q=is:issue+is:open> when
you hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#90959 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD24BUHNT7QUNHSW7HP26STR3HG53ANCNFSM4M5QNRLQ>
.
|
/retest |
/retest Review the full test history for this PR. Silence the bot with an |
1 similar comment
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
1 similar comment
/retest |
What type of PR is this?
What this PR does / why we need it:
Before the version of kubernetes 1.15 , when use
kubectl exec --help
https://github.com/kubernetes/kubernetes/blob/release-1.14/pkg/kubectl/cmd/exec/exec.go#L42
the pod name is
123456-7890
, hard to understandAfter this version , the pod name
123456-7890
has changed tomypod
https://github.com/kubernetes/kubernetes/blob/release-1.18/staging/src/k8s.io/kubectl/pkg/cmd/exec/exec.go#L46
So the kubectl cmd attach description should follow the kubectl cmd exec description.
the pod name of documentation
mypod
is better for understanding.