Epic Goal

Right now, the gRPC implementation in the PoC code requires HTTP/2 connections between the agents and the principal for bidirectional gRPC streams. However, in some environments, HTTP/2 might not yet be available, for example through usage of non-HTTP/2 compliant reverse proxies, ingresses or other Layer 7 network components in the route (some of those accept HTTP/2 on the front, but will transform to HTTP/1.1).

However, gRPC bidirectional streams have HTTP/2 as a fundamental requirement. If we’d like to support HTTP/1 as well, we will need to implement unidirectional streams as a fallback mechanism. Unidirectional streams will be less resource efficient on the network layer.

See parent feature and outcome for details.

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment