-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Unhealthy fleet server in multiple space #186045
Comments
Pinging @elastic/fleet (Team:Fleet) |
To make sure I understand what is happening: In this case there is actually a Fleet server, and agents could enroll with it, but the agent running Fleet server is not visible in this space? |
Yes that's correct, currently the check happen client side we retrieve all the fleet server agents and check if one is healthy. With spaces we probably want to change that to have that information retrieved server side, and probably check if there one healthy Fleet server accross all spaces. |
I think with the changes in #181357, all the checks for the enrollment flyout are happening server-side now, so it should be possible to bypass spaces during the check for fleet server agents. |
That's great so it probably just fixing how we retrieve the agents there to check thought all namespaces |
Description
As part of making Fleet space aware, it is possible there is no healthy Fleet server running in that space, we should define what we should do in that case as it's blocking agent enrollment
The text was updated successfully, but these errors were encountered: