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.

Sign up for GitHub

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

Jump to bottom

Service port-forwards torn down between redeploys even though service is unchanged #4518

Open
briandealwis opened this issue Jul 21, 2020 · 1 comment
Open

Service port-forwards torn down between redeploys even though service is unchanged #4518

briandealwis opened this issue Jul 21, 2020 · 1 comment
Labels
area/dev area/portforward kind/friction Issues causing user pain that do not have a workaround priority/p2 May take a couple of releases

Comments

@briandealwis
Copy link
Member

On a redeploy during dev, the port-forwards for a service are torn down even though they are unchanged. As a result, refreshing a browser after making a change can lead to a page load failure.port
@briandealwis briandealwis added area/portforward area/dev kind/friction Issues causing user pain that do not have a workaround july-chill labels Jul 21, 2020
@briandealwis
Copy link
Member Author

I haven't tracked down where it happens, but it seems this behaviour is necessary as kubectl port-forward service/xxx just points to the first pod. kubernetes/kubernetes#15180 (comment) notes:

the port forward is not re-evaluated when the pod dies. so, do a rolling upgrade and the port forward breaks.

@briandealwis briandealwis self-assigned this Jul 22, 2020
@briandealwis briandealwis mentioned this issue Jul 27, 2020
Closed
@briandealwis briandealwis added priority/p2 May take a couple of releases and removed july-chill labels Jul 31, 2020
@nkubala nkubala added this to the Icebox [P2+] milestone Sep 1, 2020
@briandealwis briandealwis removed their assignment Apr 7, 2021
@nkubala nkubala removed this from the Icebox [P2+] milestone May 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/dev area/portforward kind/friction Issues causing user pain that do not have a workaround priority/p2 May take a couple of releases
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@briandealwis @nkubala