Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add support for non-default namespace #133
What were you trying to do?
Run telepresence when the context namespace is non-default
What did you expect to happen?
run telepresence on
What happened instead?
The telepresence failed to connect to running pod with message
The pod was created properly inside the
Automatically included information
If I use:
telepresence --new-deployment test --run-shell --namespace mynamespace
It works as expected. Though documentation clearly states what I was expecting but doesn't work as such:
Reading the code it's possible the error you're seeing was due to another problem. For example, if it's taking too long for Kubernetes to download the image the pod won't get started before the timeout. In which case it worked the second time simply because the image finished downloading.
Next I will try to reproduce this myself.
What I'm seeing so far is that
$ kubectl config set-context telepresence-testing --namespace=test Context "telepresence-testing" set. $ kubectl get pod --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE default myserver-2686457485-3x4d2 1/1 Running 0 2h default testing-b5a1f69-0-5760853290557861-10841-4163343846-qp9kq 1/1 Running 0 2d kube-system fluentd-gcp-v2.0-649t4 1/1 Running 0 2d kube-system heapster-v1.3.0-4004699650-pdvdb 2/2 Running 0 2d kube-system kube-dns-806549836-tjzv9 3/3 Running 0 2d kube-system kube-dns-autoscaler-2528518105-71h6z 1/1 Running 0 2d kube-system kube-proxy-gke-telepresence-testing-pool-399ecba5-jmlr 1/1 Running 0 2d kube-system kubernetes-dashboard-2917854236-0v9jk 1/1 Running 0 2d kube-system l7-default-backend-1044750973-5xmbn 1/1 Running 0 2d $ kubectl get pod --namespace=test No resources found. $ kubectl get pod NAME READY STATUS RESTARTS AGE myserver-2686457485-3x4d2 1/1 Running 0 2h testing-b5a1f69-0-5760853290557861-10841-4163343846-qp9kq 1/1 Running 0 2d