Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Failure of kubectl logs is fatal to the Telepresence session #598
I am trying to set up Telepresence and am unable to connect to our kops-configured k8s cluster running in AWS. Any help appreciated. I don't really understand the error messages I'm seeing, except for trying to proxy logs, which fails because we currently have a non-standard logging setup in the k8s cluster.
Sorry about the crash. As you point out,
If you cannot enable
And of course we should fix
referenced this issue
May 14, 2018
This workaround works super well (as does telepresence in general!
We currently use the fluentd docker logs driver, and while we hope to switch to the tail input filter in fluentd (seems to be the standard) in the next year or so, we really want to make telepresence part of our developer toolkit sooner than that and don't really want to fork/build the project just to comment out the kubectl logs subprocess.
I'm happy to attempt a PR, but I'm admittedly not the best developer...
We want to fix this issue, i.e. make
Separately, we want to support other logging too, on a case-by-case basis, but we’re currently busy with either 1) requests/bugs from paying customers and 2) features that have broader community interest so it might be a while before we get to this.
Can you file an issue specifically for your case, the fluentd stuff? Thanks.