Use Case

TODO

User Experience

• Pooled HTTP/2 connections can be reused

Risks/Unknowns

• None

Acceptance Criteria

Implementation Requirements

• Ensure the HTTP/2 SETTINGS_ENABLE_CONNECT_PROTOCOL setting is enabled for requests to cloud.mongodb.com
• There are two parts:
  • Ensure HTTP/2 from browser to LB (if supported)
  • Ensure HTTP/2 from LB to service
    • We should be able to confirm via logs / telemetry that only a single connection is created between the LB and each service pod, because in theory envoy should be able to multiplex arbitrarily many WebSockets over a single HTTP/2 connection. If this isn't happening, ideally we should fix it or at least understand why.

Testing Requirements

• Synthetic test coverage to verify LB in stage/prod continue to serve http/2 requests with these settings.

References

• https://grafana.corp.mongodb.com/goto/Pz7o5mPNk?orgId=20
• https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Connection_management_in_HTTP_1.x