Pinging @elastic/fleet (Team:Fleet)

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?

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

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.

@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 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

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?