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

Allow to configure the Fleet Server internal host #5554

Open
AndersonQ opened this issue Sep 18, 2024 · 1 comment
Open

Allow to configure the Fleet Server internal host #5554

AndersonQ opened this issue Sep 18, 2024 · 1 comment
Labels
Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team

Comments

@AndersonQ
Copy link
Member

Describe the enhancement:

Allow to configure the Fleet Server host used by the Elastic Agent when bootstrapping Fleet Server

Describe a specific use case for the enhancement or feature:

When using mTLS the Elastic Agent and Fleet Server should be able to use TLS certificate issued to unique names/IPs, without the need to have either certificate issued to localhost

What is the definition of done?

It's possible to bootstrap a Fleet Server using mTLS where neither Fleet Server's certificate nor the Elastic Agent's certificate are issued to localhost

@AndersonQ AndersonQ added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label Sep 18, 2024
@elasticmachine
Copy link
Collaborator

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
Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team
Projects
None yet
Development

No branches or pull requests

2 participants