Context
When services communicate over HTTPS (e.g., via ingress with TLS termination), the default HTTP transport in lib-commons does not negotiate HTTP/2. This caused a protocol mismatch issue with the Tenant Manager (DSINT-996) where configmaps pointed to an HTTPS ingress URL instead of the internal cluster service.
Problem
The custom HTTP transport used for inter-service communication doesn't configure HTTP/2 support. While intra-cluster calls currently use plain HTTP (where this isn't an issue), if someone configures an HTTPS endpoint in the future, the lack of HTTP/2 negotiation can cause silent failures or degraded performance.
Proposed Solution
Configure ForceAttemptHTTP2: true (or equivalent) in the custom transport, so that HTTPS connections automatically negotiate HTTP/2 when available.
Priority
Low — preventive improvement. The immediate issue was resolved by switching to internal service URLs (LerianStudio/midaz-firmino-gitops#404).
Context
When services communicate over HTTPS (e.g., via ingress with TLS termination), the default HTTP transport in lib-commons does not negotiate HTTP/2. This caused a protocol mismatch issue with the Tenant Manager (DSINT-996) where configmaps pointed to an HTTPS ingress URL instead of the internal cluster service.
Problem
The custom HTTP transport used for inter-service communication doesn't configure HTTP/2 support. While intra-cluster calls currently use plain HTTP (where this isn't an issue), if someone configures an HTTPS endpoint in the future, the lack of HTTP/2 negotiation can cause silent failures or degraded performance.
Proposed Solution
Configure
ForceAttemptHTTP2: true(or equivalent) in the custom transport, so that HTTPS connections automatically negotiate HTTP/2 when available.Priority
Low — preventive improvement. The immediate issue was resolved by switching to internal service URLs (LerianStudio/midaz-firmino-gitops#404).