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

--header is not used with communication to Fleet Server #6823

Open
blakerouse opened this issue Feb 11, 2025 · 1 comment
Open

--header is not used with communication to Fleet Server #6823

blakerouse opened this issue Feb 11, 2025 · 1 comment
Assignees
Labels
bug Something isn't working Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team

Comments

@blakerouse
Copy link
Contributor

Overview

At the moment during enrollment the --header flag is only used for adding headers with communication with Elasticsearch, it is not used with communication with Fleet Server. The same --header flag should be used for communication with Fleet Server.

Why?

--header is normally used for reverse proxies that have some type of filtering enabled that doesn't allow a request to be proxied to the proper backend unless a specific header is present.

At the moment we support this for Elasticsearch, but not for communication with Fleet Server.

@blakerouse blakerouse added bug Something isn't working Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team labels Feb 11, 2025
@blakerouse blakerouse self-assigned this Feb 11, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team
Projects
None yet
Development

No branches or pull requests

2 participants