Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Fleet Server] Allow multiple artifact URLs to be configured for a single policy #2586

Open
nicpenning opened this issue May 15, 2023 · 2 comments
Labels
Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team

Comments

@nicpenning
Copy link

Describe the enhancement:
Today you can configure one or more artifact repositories for air gapped networks to serve downloads but you can only assign one download URI per policy. The enhancement would be like that of the output configurations in Kibana -> Fleet -> Settings where you can then set many URIs for the Elastic agent to download updates from.

Describe a specific use case for the enhancement or feature:
The use case is that we prefer agents to use our hosted downloads but if they are unavailable to from 1 source they can try another source such as another server in the network or from the default Elastic artifacts repo. I understand a load balancer could handle this but something built in would reduce complexity.

@jlind23
Copy link
Contributor

jlind23 commented May 15, 2023

@nimarezainia is this a requirement you already heard about?

@defensivedepth
Copy link

Another plus 1 for this feature request

@ycombinator ycombinator added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label May 14, 2024
@nimarezainia nimarezainia changed the title [Artifacts] Allow multiple artifact URLs to be configured for a single policy [Fleet Server] Allow multiple artifact URLs to be configured for a single policy Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team
Projects
None yet
Development

No branches or pull requests

4 participants