Overview

Elastic Agent communication to the new elastic/fleet-server does require some changes to the Fleet gateway code. This is a minimal change that should allow Elastic Agent to communicate with either Kibana or a Fleet Server if done correctly.

Items to do

• Save and send the check-in action token (this is now used to determine what actions the Agent has or has not received)
• Add HTTP2 communication. Agent should now always try to use HTTP2 first, as this provides a performance benefit of having less TCP connections to Fleet Server.

Why

Reduce the TLS load and cloud already support HTTP2, this should be simple addition and it should degrade easily.