[aerosouund]

In environments where there is a single kube api-server instance it will try to reuse HTTP connections to a single client pod. This means that for a series of requests coming in back-to-back traffic will be not load balanced across however many replicas of the reports server are available in the cluster. Leading to wasted resource and traffic congestion on the replica with the alive connection.
This option must be used with caution, no http keepalive means higher latency. In environments where requests come in spaced out this flag is not recommended

[codecov]

Codecov Report

❌ Patch coverage is 0% with 9 lines in your changes missing coverage. Please review.
✅ Project coverage is 0.05%. Comparing base (37f9063) to head (6471f01).

Files with missing lines	Patch %	Lines
pkg/app/opts/options.go	0.00%	9 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##            main    #354      +/-   ##
========================================
- Coverage   0.05%   0.05%   -0.01%     
========================================
  Files         33      33              
  Lines      19096   19105       +9     
========================================
  Hits          11      11              
- Misses     19085   19094       +9     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.