Skip to content

[Fleet] UI for opt-in into space awareness #190171

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

Closed
nchaulet opened this issue Aug 8, 2024 · 7 comments · Fixed by #221307
Closed

[Fleet] UI for opt-in into space awareness #190171

nchaulet opened this issue Aug 8, 2024 · 7 comments · Fixed by #221307
Assignees
Labels
Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@nchaulet
Copy link
Member

nchaulet commented Aug 8, 2024

Description

#189387 PR will make space awareness opt-in via an API, we should expose this in the UI

The opt-in UI should live in the advanced section of the Fleet settings and only accessible to an admin operator (with All privileges for agents, agent policies and settings)

API to opt in

POST /internal/fleet/enable_space_awareness

If space awareness is already enabled, the UI to opt in should not be present.

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

Pinging @elastic/fleet (Team:Fleet)

@cmacknz
Copy link
Member

cmacknz commented Aug 9, 2024

Where did we land on making this the default for new deployments so that we have a path to not needing this migration long term?

@nchaulet
Copy link
Member Author

nchaulet commented Aug 9, 2024

Where did we land on making this the default for new deployments so that we have a path to not needing this migration long term?

It's not done yet, I will create a follow up issue for that. Does this will be achievable before 9.0? It seems to me having that new behaviour is kind of a breaking change has a user that want to create a new deployment for a new region/testing environment will have a different behaviour that what they expect

@cmacknz
Copy link
Member

cmacknz commented Aug 12, 2024

This is definitely something we should consider for 9.0. If we made this the default mode in 9.0 that would require very user to go through this migration to get to 9.0.

@kpollich kpollich added stale Used to mark issues that were closed for being stale and removed stale Used to mark issues that were closed for being stale labels Mar 18, 2025
@nchaulet
Copy link
Member Author

nchaulet commented May 5, 2025

@sileschristian We probably will need your help on that one, to give you some context on existing cluster user will have to call an API to enable space awareness, we want to have some kind of UI for that, maybe something in Fleet settings as @nimarezainia suggested.

@sileschristian
Copy link

@sileschristian We probably will need your help on that one, to give you some context on existing cluster user will have to call an API to enable space awareness, we want to have some kind of UI for that, maybe something in Fleet settings as @nimarezainia suggested.

Sure. Sorry, where can I read more about this and @nimarezainia suggestions? Thank you

@nchaulet
Copy link
Member Author

nchaulet commented May 5, 2025

Sure. Sorry, where can I read more about this and @nimarezainia suggestions? Thank you

It seems it was dm on slack :/

We have that meta issue about spaceawareness but there is a lot of discussion https://github.com/elastic/ingest-dev/issues/1664

Trying to resume, space awareness allow to have agent policy (and related entities, agents, ...) to be space aware, so each space will have their own policies agent. This will happens automatically for new cluster, but for existing cluster we need user to opt-in for the feature as it's a breaking change, to opt-in for the feature it's an API call that only go one way, you can reverse the migration. So what we are looking here it's a way to expose in the UI that migration and trigger that API call.

Does it make things clearer?

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.

5 participants