Skip to content

Support appProtocol Field for HTTPBackendRef #2945

Open
@mpstefan

Description

@mpstefan

As a user of NGF
I want appProtocol field to be supported for HTTPBackendRefs
So that I can ensure all traffic to my application is the protocol I expect.

Acceptance

  • A BackendRef is marked as invalid if it refers to a Kubernetes Service that has an incompatible appProtocol for the given Route type.
    • The "New Standard Protocols" as outlined in GEP-3726 are included:
      • 'kubernetes.io/h2c'
      • 'kubernetes.io/ws'
      • 'kubernetes.io/wss'
  • If a Route is not able to send traffic to the backend using the specified protocol then the backend is considered invalid. Implementations MUST set the "ResolvedRefs" condition to "False" with the "UnsupportedProtocol" reason.
  • The conformance tests for the appProtocol field are enabled and pass.

Here is the originating GEP-1911

More info

Metadata

Metadata

Assignees

Labels

area/httproute/extendedRelates to all extended features of HTTPRouteenhancementNew feature or requesthighlightRelates to features that should be promoted despite not being an epicrefinedRequirements are refined and the issue is ready to be implemented.size/mediumEstimated to be completed within a week

Type

No type

Projects

Status

🏗 In Progress

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions