Summary
In environments where Kibana has internet access, but agents do not, it's common to point agents to an alternative network location to download upgraded binaries via the agent.download.sourceURI setting in agent.yml. Today, this is a manual process that doesn't scale.
What we'd like to do here is create a UI in Fleet to manage a set of custom agent binary download sources and apply those sources either globally or on a per-policy basis. The implementation and patterns here will be very similar to Fleet's outputs concepts.
Implementation
Follow up
Design mockups
Show mockups
Summary
In environments where Kibana has internet access, but agents do not, it's common to point agents to an alternative network location to download upgraded binaries via the
agent.download.sourceURIsetting inagent.yml. Today, this is a manual process that doesn't scale.What we'd like to do here is create a UI in Fleet to manage a set of custom agent binary download sources and apply those sources either globally or on a per-policy basis. The implementation and patterns here will be very similar to Fleet's
outputsconcepts.Implementation
/app/fleet/settingsthat displays an agent binary source'sname,host, anis_defaultvalue, and an actions button that open a flyout to edit the agent binary source entry [Fleet] Configure source URI in global settings and in agent policy settings #136263agent.ymlcompilation logic to honor thedefaultagent binary source or an appropriate policy-specific agent binary source [Fleet] Modify Agent policy and agent upgrades to handle custom source_uri #135629source_urivalue in agent upgrade actionsagent.download.sourceURIproperty is compiled and deployed to the appropriate agentsFollow up
source_uriin the upgrade and bulk upgrade API requestsDesign mockups
Show mockups