Skip to content

GEP: Backend Protocol Selection #1911

Closed
@dprotaso

Description

@dprotaso

/kind gep

This is an attempt to separate out the backend protocol selection from GEP-1282. This is similar to how TLS use-cases are being split out into GEP-1897

What would you like to be added:

The ability to express the protocols supported by backends.

Why this is needed:

Not all implementation support automatic protocol selection. Even in some cases protocols are disabled without an explicit opt-in (ie. websockets). Thus application developers need the ability specify the protocol of their applications.

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.kind/gepPRs related to Gateway Enhancement Proposal(GEP)lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.priority/backlogHigher priority than priority/awaiting-more-evidence.

Type

No type

Projects

Status

Implementable

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions