Skip to content

Add limitations for using the integrations synchronization feature #3538

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Oct 20, 2025
Merged

Add limitations for using the integrations synchronization feature #3538

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e402315
Add limitations for using the integrations synchronization feature
vishaangelova Oct 18, 2025
bfc59c6
Merge branch 'main' into 1853-sync-integrations-limitations
vishaangelova Oct 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions reference/fleet/automatic-integrations-synchronization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,13 @@ This feature is available only for certain subscription levels. For more informa
* Remote clusters must be running the same {{es}} version as the management cluster, or a newer version that supports {{ccr}}.
* To install integrations, remote clusters require access to the [{{package-registry}}](/reference/fleet/index.md#package-registry-intro).

## Limitations

These limitations apply when using the automatic integrations synchronization feature:

- [Index lifecycle management](/manage-data/lifecycle/index-lifecycle-management.md) (ILM) policies and enrich policies referenced in custom component templates are not automatically synchronized. Synchronizing custom assets that include references to ILM or enrich policies may cause custom component templates to break.
- Integrations installed on the management cluster are synchronized to the remote cluster regardless of the space they are installed in. On the remote cluster, the synchronized integrations are always installed in the default space.

## Configure {{ccr}} on the remote cluster

In your remote cluster:
Expand Down