Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 25 2019 16:23

    ark3 on ssh-cleanup

    (compare)

  • Jan 25 2019 16:23

    ark3 on master

    Return status rather than crash… Emit a distinct crash message f… Factor out sshuttle command and 3 more (compare)

  • Jan 25 2019 16:23
    ark3 closed #912
  • Jan 25 2019 14:57
    ark3 opened #912
  • Jan 25 2019 14:56

    ark3 on ssh-cleanup

    Return status rather than crash… Emit a distinct crash message f… Factor out sshuttle command and 2 more (compare)

  • Jan 25 2019 12:24
    bartoszmajsak opened #911
  • Jan 24 2019 22:04
    ark3 labeled #910
  • Jan 24 2019 22:04
    ark3 opened #910
  • Jan 24 2019 21:42
    ark3 closed #807
  • Jan 24 2019 21:42

    ark3 on master

    Don't pass --v=4 to kubectl eve… (compare)

  • Jan 24 2019 21:30
    ark3 closed #889
  • Jan 24 2019 21:30

    ark3 on master

    fix: changes depracated method … fix: masks logged tokens chore: adds changelog file and 8 more (compare)

  • Jan 24 2019 21:30
    ark3 closed #890
  • Jan 24 2019 21:29
    ark3 synchronize #890
  • Jan 24 2019 21:25
    ark3 closed #812
  • Jan 24 2019 21:25
    ark3 commented #812
  • Jan 24 2019 21:23
    ark3 closed #735
  • Jan 24 2019 21:23
    ark3 commented #735
  • Jan 24 2019 20:52
    rohansingh commented #905
  • Jan 24 2019 20:50
    ark3 commented #905
datawirebot
@datawirebot
<ark3> Typically Minikube is detected (by context name) and a special local cluster workaround is used. Does your cluster have a different context name, i.e. not minikube?
<teejae> using the default minikube context name for now
<ark3> Hmm. That's a bug. Could you file an issue please? I could use the telepresence.log file from a simple session, maybe just curl -svk https://kubernetes.default/api/ and curl http://google.com so I can see what happens with DNS in the log file.
datawirebot
@datawirebot
<ark3> I'm working on detecting the DNS loop without relying on context names etc. but that won't make it into the next release.
<teejae> ok. i'll have to get to that in a bit
<teejae> what is kubernetes.default? is that some well known address? i'm relatively new to kubernetes. (used to work at google, so used the borg stuff)
<teejae> sorry for all the dumb questions
datawirebot
@datawirebot
<ark3> Sorry, was distracted by something. The Kubernetes API server has a service called kubernetes in the default namespace, so that's typically a safe query.
<ark3> Thanks in advance for the issue.
datawirebot
@datawirebot
<tuckerwales> Hey guys - looking for some help if possible. I'm running Telepresence with Minikube locally, and the deployment swap seems to work fine but the deployment isn't updating when I make a change to the code. Is there something I'm doing wrong?
<ark3> Can you be more specific? What are you doing that isn't working?
<tuckerwales> I'm following the tutorial here: https://www.telepresence.io/tutorials/docker
<tuckerwales> I change the version number and save the file as directed in the tutorial, but the deployment never updates.
datawirebot
@datawirebot
<ark3> Is it fair to say that your curl command does not hit your local python process?
<tuckerwales> @ark3 yes, that's correct
datawirebot
@datawirebot
<tuckerwales> The requests hit the Docker container
<ark3> The docker container is local, i.e. on your machine. The intent of the tutorial is to let you modify running code, which is volume-mounted into the container, and see the update.
<tuckerwales> But I never see the update when I make a change to the code?
<tuckerwales> Is there something I've missed?
<ark3> No, I think I broke the tutorial. Sorry. One moment.
<tuckerwales> No problem, thanks 🙂
datawirebot
@datawirebot
<ark3> Would you mind running an experiment for me? Can you try git checkout v1.3 and then pick things up starting at docker build? That will roll back to an older version of QotM.
<tuckerwales> Sure 🙂
<ark3> Thanks, and sorry about the broken tutorial.
<tuckerwales> No problem at all...
<tuckerwales> Yup, that works @ark3. Was it Flask not being in debug mode?
<ark3> Exactly that.
<tuckerwales> Ah brilliant, we're just looking into Kubernetes/Telepresence so I didn't know if it was something else...
<tuckerwales> Thanks a lot for your help, much appreciated!
<ark3> Happy to help. I'll fix this tutorial for the 0.98 release, which will hopefully happen today.
<tuckerwales> Awesome - thanks for Ambassador/Telepresence too. We're looking to integrate both offerings, they both look very good.
<ark3> Excellent. The folks in #ambassador are very responsive. Let us know how it goes.
datawirebot
@datawirebot
<tuckerwales> Will do 🙂
datawirebot
@datawirebot
<crcornwell> hey all! i'm using telepresence to develop against a minikube cluster on an aws ec2, and i'm running into an issue opening headless chrome. i have a python flask application with an endpoint that will take and save a screenshot of a webpage by creating a subprocess that runs a node script which uses puppeteer to open headless chrome and take the screenshot. when i run this flask application using gunicorn outside of telepresence and curl into it, it manages to create the screenshot with no problem, but running it with telepresence causes it to fail with the error: TimeoutError: Timed out after 30000 ms while trying to connect to Chrome! has anyone experienced anything similar, or have any ideas about things i could try?
<crcornwell> this is using telepresence 0.97, node 9.2.1, puppeteer 1.11.0, python 2.7, flask 1.0.2 and gunicorn 19.9.0, and running on Ubuntu 18.04. if there's any other information that would be useful please let me know
datawirebot
@datawirebot
<crcornwell> well, of course i would figure it out as soon as i post here; i just noticed the message about static binaries not being supported when using --method inject-tcp, and sure enough running a telepresence shell without that flag allows the node command to complete just fine
<ark3> 🎉
<crcornwell> unfortunately i've run into some issues trying to use the default vpn-tcp method, for some reason if i swap a service deployment using that, many of my API calls fail with the error Unable to open PDO connection [wrapped: SQLSTATE[HY000] [2002] Connection refused]
<crcornwell> if i run with --method inject-tcp i don't get those errors, however
datawirebot
@datawirebot
<ark3> The key difference is that inject-tcp redirects all network traffic from the affected processes, whereas vpn-tcp redirects only traffic it thinks is for the cluster, but for all processes.
<ark3> You may need an --also-proxy to work around that. Or consider using the container method, which also redirects all network traffic and works with any container.
datawirebot
@datawirebot
<crcornwell> by the container method do you mean using --docker-run instead of --run? or is it something else?
<ark3> Yes, exactly.
datawirebot
@datawirebot
<crcornwell> ok, interesting. i'll look into that, thanks!
<ark3> @crcornwell Your usage of Telepresence is complex and interesting. Is your work open source? Can you talk about it?
<crcornwell> unfortunately it's not open source, but i can talk about it a bit
datawirebot
@datawirebot
<crcornwell> we actually just started using it, about a year ago we moved our infrastructure to kubernetes using amazon's EKS. prior to that we were just running our services manually on several machines we were renting in a datacenter
<crcornwell> after we migrated our production services to k8s, we didn't update our development environments, and so there was an increasing amount of friction between how we needed to configure our application so that it would work in production, vs how it needed to work on our dev environments
<crcornwell> so over the last month or so i've been tasked with figuring out how we could bring our development servers more in line with how things are running on production
<crcornwell> i set up a minikube cluster and deployed our application to that, and then i found telepresence which i think is what actually makes this viable for development