-
Notifications
You must be signed in to change notification settings - Fork 527
Add SPDY support for L7 load balancing #11807
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
Add SPDY support for L7 load balancing #11807
Conversation
Ensure it is set to a name which is part of any kube-apiserver certificate.
/assign |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for the enhancement. It will hopefully make rollout of L7 load-balancing feasible.
I found a few nits, though.
b6649a8
to
981f943
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
LGTM label has been added. Git tree hash: 79df776cf40e9b221093505aae0eb39a829ffe3a
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ScheererJ The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
How to categorize this PR?
/area scalability
/kind enhancement
What this PR does / why we need it:
When L7 was introduced with PR #11085 it did not include support for SPDY which is the old streaming protocol in Kubernetes. Websocket is the future protocol which is enabled by default since Kubernetes v1.31.0 (see this blog entry for more information). Thus, L7 load balancing could be enabled for Kubernetes >=v1.31.0 only.
Later, we found out that the Kubernetes Conformance tests require SPDY support until Kubernetes v1.33.0. Additionally, some of our own implementation using streaming APIs had to be adapted (see #8810 (comment)).
We decided to add SPDY support to allow users a smooth transition to websockets and pass the Conformance test when the feature is active.
This PR implements SPDY support and is following this suggestion to create a custom route configuration and a custom (envoy) cluster with no HTTP2 support in order to support upgrading the connection to SPDY.
Given the circumstances that we are using istio, there are two different options.
EnvoyFilter
sEnvoyFilter
sThis PR follows the latter approach.
It uses
EnvoyFilter
to disable HTTP2 and to set the correct upgrade configs. Both cannot be done via Istio objects. Apart from that, the existing Istio configuration is used in a slightly adapted way.Which issue(s) this PR fixes:
Part of #8810
Special notes for your reviewer:
/cc @ScheererJ @DockToFuture @hendrikKahl
Release note: