-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Envoy in telepresence agent rejects http 1.0 #3169
Labels
t:feature
New feature or enhancement request
Comments
Ok, narrowed down the bug: telepresence uses envoy to manage agent traffic. envoy, by default, rejects all http 1.0 requests. envoyproxy/envoy#170 nginx, by default, sends http 1.0 requests. http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_http_version it would be good if telepresence updated the agent's envoy config to accept http 1.0. |
thallgren
changed the title
telepresence agent kills all traffic with http error 426
Envoy in telepresence agent rejects http 1.0
Feb 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When I intercept traffic under certain conditions, Telepresence kills all traffic, even traffic that's not being intercepted.
To Reproduce
See this repro:
https://github.com/nicks/telepresence-sandbox
which has a detailed setup
Once I get into this state, all HTTP requests return error code 426
Expected behavior
I expect Telepresence to intercept the traffic that matches my header, and leave all other traffic alone.
Once telepresence gets into this state, the only way to fix it is to uninstall the agent.
Notably,
telepresence leave
does not fix the problem.tVersions (please complete the following information):
see attached repo for kubernetes
kubectl version --short
Client Version: v1.27.1
Kustomize Version: v5.0.1
Server Version: v1.25.7+k3s1
The text was updated successfully, but these errors were encountered: