Closed mumoshu closed 6 years ago
Note that kubectl run
leaves a running pod. So, it may be issue that I can't attach to the running pod created via kubectl run
automatically?
Also, kubectl attach
and kubectl exec
both worked for me. The session records are created after the interactive sessions are completed. So, the issue seems to present only in kubectl run
s.
@mumoshu thanks for reporting, but this is a kind of integration issue that would normally fall into our enterprise support category. The OSS repo is for reporting reproducible bugs. If you're interested in working with our integration engineers, please reach out to sales@gravitational.com
@kontsevoy Hi! Happy to work with them. But are you saying you can't reproduce this for the OSS ver. of Teleport? I thought that it would be reproducible given the code for the Kubernetes integration is open :)
@mumoshu I see what's happening here... looks like you're playing with features in development. We don't have anything else at this moment (other than Github) to collaborate on the ongoing work, so I'll keep this open for you to chat with devs like @klizhentas who's looking into k8s integration.
What happened:
kubectl run -i --tty ... -- bash
through the proxy does create a pod, but it never shows the bash promt.What you expected to happen:
I expect it to just show the prompt in a few seconds, like when I run
kubectl
directly against the k8s api on minikube:How to reproduce it (as minimally and precisely as possible):
Use the helm chart proposed in #2014 and run the command above.
Environment:
teleport version
): 2.7.0-alpha.3tsh version
): 2.7.0-alpha.3 (built from the HEAD of #2014)Browser environment
Relevant Debug Logs If Applicable