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

Revert "[backport v8] force http2 kubernetes #9294" #9953

Closed

Conversation

NajiObeid
Copy link
Contributor

Reverts #9796

Issue reported today about not being able to use with the http2 change I introduced kubectl exec

It turns out spdy doesn't play well with http2 and I naively thought the connection would downgrade to http1.
I also thought I tested this case.

There has been works to deprecate spdy in kubernetes but nothing concrete at the moment.
kubernetes/kubernetes#7452
kubernetes/kubernetes#89163

I won't revert the change to master as of right now as I would like to try a couple more things.

@NajiObeid NajiObeid requested a review from russjones January 26, 2022 05:44
@github-actions github-actions bot requested a review from r0mant January 26, 2022 05:45
@NajiObeid NajiObeid enabled auto-merge (squash) January 26, 2022 17:39
@russjones
Copy link
Contributor

russjones commented Jan 26, 2022

@NajiObeid How long will it take to fix this issue? If it's just a day or two it might make more sense to tell customers to just roll back to 8.1.0 instead of rolling out a revert and then the fix a few days later. What do you think?

I think a revert makes more sense if something is going to take a week+ to fix.

@russjones russjones mentioned this pull request Jan 28, 2022
@russjones russjones closed this Feb 2, 2022
auto-merge was automatically disabled February 2, 2022 21:15

Pull request was closed

@NajiObeid NajiObeid deleted the revert-9796-naji/v8/force-http2-kubernetes branch August 10, 2022 15:05
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

Successfully merging this pull request may close these issues.

2 participants