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] Unhealthy fleet server in multiple space #186045

Closed
nchaulet opened this issue Jun 11, 2024 · 5 comments · Fixed by #186322
Closed

[Fleet] Unhealthy fleet server in multiple space #186045

nchaulet opened this issue Jun 11, 2024 · 5 comments · Fixed by #186322
Assignees
Labels
Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@nchaulet
Copy link
Member

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

image

@nchaulet nchaulet added the Team:Fleet Team label for Observability Data Collection Fleet team label Jun 11, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@cmacknz
Copy link
Member

cmacknz commented Jun 11, 2024

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?

@nchaulet
Copy link
Member Author

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.

@jen-huang
Copy link
Contributor

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.

@nchaulet
Copy link
Member Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants