knative / knative/eventing

HTTP/2 support in Knative Eventing

Open
#3,312 11 comments 0 reactions 0 assignees View on GitHub
area/performance kind/feature-request priority/important-longterm roadmap triage/accepted
Dominant language
Go
Stars
1.6k
Forks
631
Avg merge
2d 1h
Merged PRs (30d)
6

Description

**Problem**
Support HTTP/2

**[Persona:](https://github.com/knative/eventing/blob/master/docs/personas.md)**
Which persona is this feature for? Users/Developers

**Exit Criteria**

* All Knative Eventing components supports HTTP/2 transparently
* Users should be able to use HTTP/2 with possibly little/zero configuration
* Support HTTP/2 in the full event flow

**Additional context (optional)**
I propose to support HTTP/2 with:

* TLS ALPN (HTTP/2 Encrypted)
* H2C (HTTP/2 Cleartext) with H2C Upgrade

Both the http clients and http servers we use should support it transparently

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are identified in the issue. Start by mapping every Knative Eventing HTTP client and server across the full event flow, then verify that TLS ALPN and H2C work transparently with little or no configuration in all components.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
backend-api-design, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.