[k8s.io] Kubectl client [k8s.io] Simple pod should support exec through an HTTP proxy {Kubernetes e2e suite} #30489

k8s-github-robot · 2016-08-12T01:57:24Z

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-soak-continuous-e2e-gke/8167/

Failed: [k8s.io] Kubectl client [k8s.io] Simple pod should support exec through an HTTP proxy {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:277
Expected
    <bool>: false
to be true
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:276

Previous issues for this test: #27156 #28979

The text was updated successfully, but these errors were encountered:

k8s-github-robot · 2016-08-18T02:38:52Z

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/30814/kubernetes-pull-build-test-e2e-gce/54259/

Failed: [k8s.io] Kubectl client [k8s.io] Simple pod should support exec through an HTTP proxy {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:349
Aug 17 19:18:06.500: Unexpected kubectl exec output. Wanted "running in container\n", got  ""
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:338

Happened on a presubmit run in #30814.

k8s-github-robot · 2016-08-22T00:59:07Z

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-staging-parallel/7469/

Failed: [k8s.io] Kubectl client [k8s.io] Simple pod should support exec through an HTTP proxy {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:348
Expected error:
    <*errors.errorString | 0xc820bb08b0>: {
        s: "Error running &{/workspace/kubernetes/platforms/linux/amd64/kubectl [kubectl --server=https://104.154.233.4 --kubeconfig=/workspace/.kube/config --namespace=e2e-tests-kubectl-oicod exec nginx echo running in container] [ZONE=us-central1-f BUILD_URL=http://goto.google.com/k8s-test/job/kubernetes-e2e-gke-staging-parallel/7469/ JENKINS_AWS_SSH_PUBLIC_KEY_FILE=/var/lib/jenkins/workspace/kubernetes-e2e-gke-staging-parallel@tmp/secretFiles/95c6ce69-fa1a-4cbf-b741-6c01855ddcf9/kube_aws_rsa.pub.txt GOLANG_VERSION=1.6.3 HOSTNAME=432c700ab4e0 CLOUDSDK_COMPONENT_MANAGER_DISABLE_UPDATE_CHECK=true ROOT_BUILD_CAUSE_TIMERTRIGGER=true TERM=xterm HUDSON_SERVER_COOKIE=02143c9ae5889f5c SHELL=/bin/bash PROJECT=k8s-e2e-gke-staging-parallel KUBE_GCE_INSTANCE_PREFIX=jenkins-e2e JENKINS_AWS_SSH_PRIVATE_KEY_FILE=/var/lib/jenkins/workspace/kubernetes-e2e-gke-staging-parallel@tmp/secretFiles/f6aecaa7-deca-45cb-b2aa-93297f75630f/kube_aws_rsa.txt SSH_CLIENT=10.240.0.37 50821 22 KUBE_CONFIG_FILE=config-test.sh GOOGLE_APPLICATION_CREDENTIALS=/service-account.json BUILD_TAG=jenkins-kubernetes-e2e-gke-staging-parallel-7469 E2E_UP=true CLUSTER_NAME=jenkins-e2e ROOT_BUILD_CAUSE=TIMERTRIGGER CLOUDSDK_COMPONENT_MANAGER_SNAPSHOT_URL=file:///workspace/repo/components-2.json WORKSPACE=/workspace JOB_URL=http://goto.google.com/k8s-test/job/kubernetes-e2e-gke-staging-parallel/ JENKINS_AWS_CREDENTIALS_FILE=/var/lib/jenkins/workspace/kubernetes-e2e-gke-staging-parallel@tmp/secretFiles/9e846514-4509-4bdc-bb7c-3c3ce9b0a269/aws_credentials.txt USER=jenkins KUBE_GCE_NETWORK=jenkins-e2e CLOUDSDK_CONFIG=/var/lib/jenkins/.config/gcloud E2E_REPORT_DIR=/workspace/_artifacts INSTANCE_PREFIX=jenkins-e2e JENKINS_GCE_SSH_PRIVATE_KEY_FILE=/var/lib/jenkins/workspace/kubernetes-e2e-gke-staging-parallel@tmp/secretFiles/c926eb6c-c4a4-4db9-b78b-ea978a7efa4c/google_compute_engine.txt REPO_DIR=/var/lib/jenkins/workspace/kubernetes-e2e-gke-staging-parallel GINKGO_TEST_ARGS=--ginkgo.skip=\\[Slow\\]|\\[Serial\\]|\\[Disruptive\\]|\\[Flaky\\]|\\[Feature:.+\\] NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat JENKINS_HOME=/var/lib/jenkins CLOUDSDK_CORE_DISABLE_PROMPTS=1 JENKINS_USE_SERVER_VERSION=y MAIL=/var/mail/jenkins PATH=/workspace/kubernetes/platforms/linux/amd64:/workspace/cloudsdk/google-cloud-sdk/bin://google-cloud-sdk/bin:/go/bin:/usr/local/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin E2E_OPT=--check_version_skew=false PWD=/workspace/kubernetes CLOUDSDK_BUCKET=gs://cloud-sdk-testing/rc HUDSON_URL=http://goto.google.com/k8s-test/ LANG=en_US.UTF-8 E2E_TEST=true JOB_NAME=kubernetes-e2e-gke-staging-parallel KUBECTL=./cluster/kubectl.sh HOST_ARTIFACTS_DIR=/var/lib/jenkins/workspace/kubernetes-e2e-gke-staging-parallel/_artifacts BUILD_DISPLAY_NAME=#7469 XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt KUBERNETES_PROVIDER=gke JENKINS_URL=http://goto.google.com/k8s-test/ BUILD_CAUSE=TIMERTRIGGER BUILD_ID=7469 GOLANG_DOWNLOAD_SHA256=cdde5e08530c0579255d6153b08fdb3b8e47caabbe717bc7bcd7561275a87aeb KUBE_GKE_NETWORK=jenkins-e2e CLOUDSDK_API_ENDPOINT_OVERRIDES_CONTAINER=https://staging-container.sandbox.googleapis.com/ JOB_BASE_NAME=kubernetes-e2e-gke-staging-parallel E2E_MIN_STARTUP_PODS=8 HOME=/workspace SHLVL=6 no_proxy=127.0.0.1,localhost JENKINS_SERVER_COOKIE=02143c9ae5889f5c EXECUTOR_NUMBER=0 KUBE_GCE_ZONE=us-central1-f JENKINS_GCE_SSH_PUBLIC_KEY_FILE=/var/lib/jenkins/workspace/kubernetes-e2e-gke-staging-parallel@tmp/secretFiles/720d4d04-da89-4d85-9548-bb7284574659/google_compute_engine.pub.txt NODE_LABELS=agent-light-4 e2e node GINKGO_PARALLEL=y LOGNAME=jenkins HUDSON_HOME=/var/lib/jenkins SSH_CONNECTION=10.240.0.37 50821 10.240.0.57 22 NODE_NAME=agent-light-4 BUILD_CAUSE_TIMERTRIGGER=true E2E_PUBLISH_GREEN_VERSION=false GOPATH=/go KUBE_AWS_INSTANCE_PREFIX=jenkins-e2e BUILD_NUMBER=7469 HUDSON_COOKIE=460abfeb-ddd6-4c36-87e5-d44a239d8a20 FAIL_ON_GCP_RESOURCE_LEAK=true E2E_DOWN=true GOLANG_DOWNLOAD_URL=https://golang.org/dl/go1.6.3.linux-amd64.tar.gz _=/workspace/kubernetes/platforms/linux/amd64/ginkgo HTTPS_PROXY=http://127.0.0.1:45606]  <nil>  Error from server: ssh: unexpected packet in response to channel open: <nil>\n [] <nil> 0xc82097f260 exit status 1 <nil> true [0xc82029e588 0xc82029e5a0 0xc82029e5b8] [0xc82029e588 0xc82029e5a0 0xc82029e5b8] [0xc82029e598 0xc82029e5b0] [0xa96280 0xa96280] 0xc820a71500}:\nCommand stdout:\n\nstderr:\nError from server: ssh: unexpected packet in response to channel open: <nil>\n\nerror:\nexit status 1\n",
    }
    Error running &{/workspace/kubernetes/platforms/linux/amd64/kubectl [kubectl --server=https://104.154.233.4 --kubeconfig=/workspace/.kube/config --namespace=e2e-tests-kubectl-oicod exec nginx echo running in container] [ZONE=us-central1-f BUILD_URL=http://goto.google.com/k8s-test/job/kubernetes-e2e-gke-staging-parallel/7469/ JENKINS_AWS_SSH_PUBLIC_KEY_FILE=/var/lib/jenkins/workspace/kubernetes-e2e-gke-staging-parallel@tmp/secretFiles/95c6ce69-fa1a-4cbf-b741-6c01855ddcf9/kube_aws_rsa.pub.txt GOLANG_VERSION=1.6.3 HOSTNAME=432c700ab4e0 CLOUDSDK_COMPONENT_MANAGER_DISABLE_UPDATE_CHECK=true ROOT_BUILD_CAUSE_TIMERTRIGGER=true TERM=xterm HUDSON_SERVER_COOKIE=02143c9ae5889f5c SHELL=/bin/bash PROJECT=k8s-e2e-gke-staging-parallel KUBE_GCE_INSTANCE_PREFIX=jenkins-e2e JENKINS_AWS_SSH_PRIVATE_KEY_FILE=/var/lib/jenkins/workspace/kubernetes-e2e-gke-staging-parallel@tmp/secretFiles/f6aecaa7-deca-45cb-b2aa-93297f75630f/kube_aws_rsa.txt SSH_CLIENT=10.240.0.37 50821 22 KUBE_CONFIG_FILE=config-test.sh GOOGLE_APPLICATION_CREDENTIALS=/service-account.json BUILD_TAG=jenkins-kubernetes-e2e-gke-staging-parallel-7469 E2E_UP=true CLUSTER_NAME=jenkins-e2e ROOT_BUILD_CAUSE=TIMERTRIGGER CLOUDSDK_COMPONENT_MANAGER_SNAPSHOT_URL=file:///workspace/repo/components-2.json WORKSPACE=/workspace JOB_URL=http://goto.google.com/k8s-test/job/kubernetes-e2e-gke-staging-parallel/ JENKINS_AWS_CREDENTIALS_FILE=/var/lib/jenkins/workspace/kubernetes-e2e-gke-staging-parallel@tmp/secretFiles/9e846514-4509-4bdc-bb7c-3c3ce9b0a269/aws_credentials.txt USER=jenkins KUBE_GCE_NETWORK=jenkins-e2e CLOUDSDK_CONFIG=/var/lib/jenkins/.config/gcloud E2E_REPORT_DIR=/workspace/_artifacts INSTANCE_PREFIX=jenkins-e2e JENKINS_GCE_SSH_PRIVATE_KEY_FILE=/var/lib/jenkins/workspace/kubernetes-e2e-gke-staging-parallel@tmp/secretFiles/c926eb6c-c4a4-4db9-b78b-ea978a7efa4c/google_compute_engine.txt REPO_DIR=/var/lib/jenkins/workspace/kubernetes-e2e-gke-staging-parallel GINKGO_TEST_ARGS=--ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\] NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat JENKINS_HOME=/var/lib/jenkins CLOUDSDK_CORE_DISABLE_PROMPTS=1 JENKINS_USE_SERVER_VERSION=y MAIL=/var/mail/jenkins PATH=/workspace/kubernetes/platforms/linux/amd64:/workspace/cloudsdk/google-cloud-sdk/bin://google-cloud-sdk/bin:/go/bin:/usr/local/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin E2E_OPT=--check_version_skew=false PWD=/workspace/kubernetes CLOUDSDK_BUCKET=gs://cloud-sdk-testing/rc HUDSON_URL=http://goto.google.com/k8s-test/ LANG=en_US.UTF-8 E2E_TEST=true JOB_NAME=kubernetes-e2e-gke-staging-parallel KUBECTL=./cluster/kubectl.sh HOST_ARTIFACTS_DIR=/var/lib/jenkins/workspace/kubernetes-e2e-gke-staging-parallel/_artifacts BUILD_DISPLAY_NAME=#7469 XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt KUBERNETES_PROVIDER=gke JENKINS_URL=http://goto.google.com/k8s-test/ BUILD_CAUSE=TIMERTRIGGER BUILD_ID=7469 GOLANG_DOWNLOAD_SHA256=cdde5e08530c0579255d6153b08fdb3b8e47caabbe717bc7bcd7561275a87aeb KUBE_GKE_NETWORK=jenkins-e2e CLOUDSDK_API_ENDPOINT_OVERRIDES_CONTAINER=https://staging-container.sandbox.googleapis.com/ JOB_BASE_NAME=kubernetes-e2e-gke-staging-parallel E2E_MIN_STARTUP_PODS=8 HOME=/workspace SHLVL=6 no_proxy=127.0.0.1,localhost JENKINS_SERVER_COOKIE=02143c9ae5889f5c EXECUTOR_NUMBER=0 KUBE_GCE_ZONE=us-central1-f JENKINS_GCE_SSH_PUBLIC_KEY_FILE=/var/lib/jenkins/workspace/kubernetes-e2e-gke-staging-parallel@tmp/secretFiles/720d4d04-da89-4d85-9548-bb7284574659/google_compute_engine.pub.txt NODE_LABELS=agent-light-4 e2e node GINKGO_PARALLEL=y LOGNAME=jenkins HUDSON_HOME=/var/lib/jenkins SSH_CONNECTION=10.240.0.37 50821 10.240.0.57 22 NODE_NAME=agent-light-4 BUILD_CAUSE_TIMERTRIGGER=true E2E_PUBLISH_GREEN_VERSION=false GOPATH=/go KUBE_AWS_INSTANCE_PREFIX=jenkins-e2e BUILD_NUMBER=7469 HUDSON_COOKIE=460abfeb-ddd6-4c36-87e5-d44a239d8a20 FAIL_ON_GCP_RESOURCE_LEAK=true E2E_DOWN=true GOLANG_DOWNLOAD_URL=https://golang.org/dl/go1.6.3.linux-amd64.tar.gz _=/workspace/kubernetes/platforms/linux/amd64/ginkgo HTTPS_PROXY=http://127.0.0.1:45606]  <nil>  Error from server: ssh: unexpected packet in response to channel open: <nil>
     [] <nil> 0xc82097f260 exit status 1 <nil> true [0xc82029e588 0xc82029e5a0 0xc82029e5b8] [0xc82029e588 0xc82029e5a0 0xc82029e5b8] [0xc82029e598 0xc82029e5b0] [0xa96280 0xa96280] 0xc820a71500}:
    Command stdout:

    stderr:
    Error from server: ssh: unexpected packet in response to channel open: <nil>

    error:
    exit status 1

not to have occurred

ncdc · 2016-08-25T14:30:04Z

The initial comment (#30489 (comment)) wasn't related to exec at all - BeforeEach failed trying to run a pod. I'm unable to locate the appropriate data in the log files to triage.

The error from the second comment (Unexpected kubectl exec output. Wanted "running in container\n", got "") is a legit flake, but I'm having trouble figuring out why it failed. The exec request made its way from kubectl to apiserver to kubelet. Kubelet finished running it quickly. The apiserver returned a response to kubectl quickly (albeit the empty string) at 02:18:06.500. The apiserver shows Error proxying data from client to backend: read tcp 10.240.0.2:443->146.148.49.195:59778: read: connection reset by peer at 02:18:33.703557. It's unclear if this is related to this exec call, however. Finally, at 02:19:44.427668, the apiserver logs that the exec call finished, 1m38s after kubectl issued it.

For the last comment, I assume that Error from server: ssh: unexpected packet in response to channel open: <nil> is related to the ssh connection from apiserver to node?

@pwittrock I don't know how to resolve this flake. What do you recommend doing here?

k8s-github-robot · 2016-08-29T21:42:26Z

[FLAKE-PING] @ncdc

This flaky-test issue would love to have more attention...

ncdc · 2016-09-01T20:18:55Z

@pwittrock bump if you have a moment

pwittrock · 2016-09-01T22:10:09Z

@bprashanth Would you be able to help @ncdc on this, or find someone who can?

pwittrock · 2016-09-01T22:10:28Z

@ncdc Apologies for my unresponsiveness. Thank you for following up on this.

bprashanth · 2016-09-01T22:19:01Z

I'm not That familiar with exec, ignore that last one till I or someone has time to dig since it's GKE (@cjcullen), the previous failures should be standard kubectl exec (it still uses spdy right?). connection reset by peer is usually rst, or remote end has dropped the connection, suggest digging into node readiness/kubelet health if the exec actually got its connection dropped.

k8s-github-robot · 2016-09-05T22:24:34Z

[FLAKE-PING] @ncdc

This flaky-test issue would love to have more attention.

ncdc · 2016-09-07T19:43:19Z

@bprashanth it turns out that Error proxying data from client to backend: read tcp 10.240.0.2:443->146.148.49.195:59778: read: connection reset by peer was related to a port-forwarding call, and not the exec one that failed.

If you look at the apiserver log, you see these entries one right after the other:

I0818 02:19:44.427522       5 handlers.go:164] POST /api/v1/namespaces/e2e-tests-kubectl-z139p/pods/nginx/exec?command=echo&command=running&command=in&command=container&container=nginx&container=nginx&stderr=true&stdout=true: (1m20.970723096s) hijacked [[kubectl/v1.4.0 (linux/amd64) kubernetes/b9f294d] 146.148.49.195:59752]
I0818 02:19:44.427668       5 handlers.go:164] POST /api/v1/namespaces/e2e-tests-kubectl-k1h1c/pods/nginx/exec?command=echo&command=running&command=in&command=container&container=nginx&container=nginx&stderr=true&stdout=true: (1m38.126429034s) hijacked [[kubectl/v1.4.0 (linux/amd64) kubernetes/b9f294d] 146.148.49.195:59710]
I0818 02:19:44.427912       5 handlers.go:164] POST /api/v1/namespaces/e2e-tests-kubectl-z139p/pods/nginx/exec?command=echo&command=running&command=in&command=container&container=nginx&container=nginx&stderr=true&stdout=true: (1m20.72111347s) hijacked [[kubectl/v1.4.0 (linux/amd64) kubernetes/b9f294d] 146.148.49.195:59756]

There's something strange going on:

19:18:23.325, start exec for namespace e2e-tests-kubectl-z139p
1. Build log reports results at 19:18:23.575
2. Apiserver log reports hijacking ended at 19:19:44.427522
19:18:06.170, start exec for namespace e2e-tests-kubectl-k1h1c
Build log reports results at 19:18:06.500
Apiserver log reports hijacking ended at 19:19:44.427668
19:18:23.955, start exec for namespace e2e-tests-kubectl-z139p
1. Build log reports results at 19:18:23.829
2. Apiserver log reports hijacking ended at 19:19:44.427912

I'm not sure why there is a gap of over 1 minute between the time kubectl got a response from the apiserver and when the apiserver considered the request finished. I'm also still not sure why one of these exec requests didn't get any data. Maybe the latter is similar to whatever is going on in #27680.

@smarterclayton any ideas why the apiserver has a huge gap in logging the hijacking?

smarterclayton · 2016-09-07T23:42:44Z

Nothing comes to mind

k8s-github-robot · 2016-09-11T23:49:07Z

[FLAKE-PING] @ncdc

This flaky-test issue would love to have more attention.

k8s-github-robot · 2016-09-15T23:55:15Z

[FLAKE-PING] @ncdc

This flaky-test issue would love to have more attention.

k8s-github-robot · 2016-09-19T23:55:37Z

[FLAKE-PING] @ncdc

This flaky-test issue would love to have more attention.

k8s-github-robot assigned ncdc Aug 12, 2016

k8s-github-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. kind/flake Categorizes issue or PR as related to a flaky test. labels Aug 12, 2016

k8s-github-robot mentioned this issue Aug 13, 2016

kubernetes-e2e-gke: broken test run #28656

Closed

k8s-github-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/backlog Higher priority than priority/awaiting-more-evidence. labels Aug 22, 2016

This was referenced Aug 23, 2016

kubernetes-e2e-gke-staging-parallel: broken test run #31201

Closed

kubernetes-e2e-gke: broken test run #31188

Closed

pwittrock added the flake-needs-czar-attention-release-1.4 label Aug 25, 2016

k8s-github-robot mentioned this issue Aug 27, 2016

kubernetes-soak-continuous-e2e-gce: broken test run #31503

Closed

pwittrock removed the flake-needs-czar-attention-release-1.4 label Sep 1, 2016

k8s-github-robot mentioned this issue Sep 5, 2016

kubernetes-e2e-gke-staging-parallel: broken test run #31855

Closed

k8s-github-robot mentioned this issue Sep 7, 2016

kubernetes-soak-continuous-e2e-gke: broken test run #30175

Closed

bprashanth mentioned this issue Sep 8, 2016

Investigate "ssh: unexpected packet in response to channel" on GKE #32248

Closed

ncdc added the non-release-blocker label Sep 8, 2016

k8s-github-robot mentioned this issue Sep 9, 2016

kubernetes-e2e-gke: broken test run #32345

Closed

This was referenced Mar 10, 2017

ci-kubernetes-e2e-gci-gce: broken test run #42159

Closed

ci-kubernetes-e2e-kops-aws: broken test run #42334

Closed

ci-kubernetes-e2e-gci-gke-prod: broken test run #43036

Closed

This was referenced Mar 28, 2017

ci-kubernetes-e2e-gci-gce-proto: broken test run #43454

Closed

ci-kubernetes-e2e-gce-multizone: broken test run #43191

Closed

ci-kubernetes-e2e-gci-gce-etcd3: broken test run #43520

Closed

ci-kubernetes-e2e-gci-gke-staging: broken test run #43037

Closed

k8s-github-robot mentioned this issue Apr 5, 2017

ci-kubernetes-e2e-gke-staging: broken test run #42792

Closed

This was referenced Apr 19, 2017

ci-kubernetes-e2e-kops-aws-release-1.6: broken test run #42643

Closed

ci-kubernetes-e2e-gke-staging-parallel: broken test run #42816

Closed

ci-kubernetes-e2e-gci-gke-subnet: broken test run #43283

Closed

k8s-github-robot mentioned this issue Apr 29, 2017

ci-kubernetes-e2e-gci-gke-test: broken test run #44699

Closed

dymurray mentioned this issue Jan 16, 2019

pkg/ansible/proxy; Do not inject owner references on subresource requests operator-framework/operator-sdk#929

Merged

limhawjia mentioned this issue Dec 19, 2022

chore(e2e-tests): add e2e test ci config kubewharf/enhanced-k8s#1

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[k8s.io] Kubectl client [k8s.io] Simple pod should support exec through an HTTP proxy {Kubernetes e2e suite} #30489

[k8s.io] Kubectl client [k8s.io] Simple pod should support exec through an HTTP proxy {Kubernetes e2e suite} #30489

k8s-github-robot commented Aug 12, 2016

k8s-github-robot commented Aug 18, 2016

k8s-github-robot commented Aug 22, 2016

ncdc commented Aug 25, 2016

k8s-github-robot commented Aug 29, 2016

ncdc commented Sep 1, 2016

pwittrock commented Sep 1, 2016

pwittrock commented Sep 1, 2016

bprashanth commented Sep 1, 2016

k8s-github-robot commented Sep 5, 2016

ncdc commented Sep 7, 2016

smarterclayton commented Sep 7, 2016 via email

k8s-github-robot commented Sep 11, 2016

k8s-github-robot commented Sep 15, 2016

k8s-github-robot commented Sep 19, 2016

[k8s.io] Kubectl client [k8s.io] Simple pod should support exec through an HTTP proxy {Kubernetes e2e suite} #30489

[k8s.io] Kubectl client [k8s.io] Simple pod should support exec through an HTTP proxy {Kubernetes e2e suite} #30489

Comments

k8s-github-robot commented Aug 12, 2016

k8s-github-robot commented Aug 18, 2016

k8s-github-robot commented Aug 22, 2016

ncdc commented Aug 25, 2016

k8s-github-robot commented Aug 29, 2016

ncdc commented Sep 1, 2016

pwittrock commented Sep 1, 2016

pwittrock commented Sep 1, 2016

bprashanth commented Sep 1, 2016

k8s-github-robot commented Sep 5, 2016

ncdc commented Sep 7, 2016

smarterclayton commented Sep 7, 2016 via email

k8s-github-robot commented Sep 11, 2016

k8s-github-robot commented Sep 15, 2016

k8s-github-robot commented Sep 19, 2016