[Fleet] [Meta] Incremental improvements for using Fleet/Integrations across multiple spaces

[kpollich]

This is a meta issue to track incremental improvements for Fleet's multi-space support. We have a larger project being defined to embrace multi-space environments for Fleet/Integrations, but this issue does not track that project. The goal of this issue is to gather common bugs, papercut items, and pain points with multiple spaces and Fleet today that we can improve incrementally while the larger multi-space project is being defined.

References

• Multiple issues - Fleet integrations across multiple spaces confuses Kibana/Fleet integrations#3434
• Not fixed in 8.9.1 / Integrations in multiple Kibana Spaces #164243

Common problems

Broadly, we've observed the following common problems when multiple spaces are in use with Fleet/Integrations

• Saved objects conflicts, specifically with tag objects are very frequent
• Installation status can become stuck in installing when conflicts with objects in other spaces are encountered
• Upgrading integration policies is not space aware, and can result in orphaned/desynced integration policies in multiple spaces

Child issues

Beta Give feedback

1. [Fleet] Make Fleet's managed data views global across spaces #172009
   Team:Fleet +1
   
2. [Fleet] Prevent saved object tag conflicts when installing integrations in multiple spaces #172960
   Team:Fleet +1
   
3. [Fleet] Saved objects conflicts shouldn't throw Concurrent Installation error #171986
   Team:Fleet +1
   
4. [Fleet] Integration policy upgrades are not space aware #172961
   Team:Fleet +1
   
5. [Fleet] Fleet should allow an integration to be installed/reinstalled into another space #172963
   QA:Validated Team:Elastic-Agent-Control-Plane Team:Fleet +3
   
6. Create public documentation for known limitations and common "gotchas" for using Fleet/Integrations across multiple spaces

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[amitkanfer]

detailed problems in this comment from a community member

[kpollich]

I'm closing this as completed as #172963 is the only remaining issue here and it's tracked in the broader RBAC workstream.