Skip to content
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

How to deal with port-forward timeouts #12

Open
atgreen opened this issue May 16, 2020 · 1 comment
Open

How to deal with port-forward timeouts #12

atgreen opened this issue May 16, 2020 · 1 comment

Comments

@atgreen
Copy link
Member

atgreen commented May 16, 2020

My k8s is timing out port-forwards, which is annoying for sly debugging. Of course, this is configurable at the kubelet layer, but it would be nice to figure out a way to support users who don't have this level of access. Exposing 4005 via nodeport or similar also seems bad because of the lack of auth.

@atgreen
Copy link
Member Author

atgreen commented Jun 1, 2020

My timeouts didn't come from openshift. They were from the haproxy load balancer in front of ocp api server. My haproxy was configured thusly...

    timeout connect         5s
    timeout client          30s
    timeout server          30s

Setting tunnel and client-fin timeouts appear to solve the problem:

    timeout connect         5s
    timeout client          30s
    timeout server          30s
    timeout client-fin      30s
    timeout tunnel          1h # timeout for use with oc port-forward

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant