elasticsearch/docs/reference/modules/remote-clusters-shared.asci...

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

29 lines
2.1 KiB
Plaintext
Raw Normal View History

// tag::remote-cluster-compatibility-matrix[]
[cols="^,^,^,^,^,^,^,^,^,^"]
|====
| 9+^h| Local cluster
h| Remote cluster | 5.05.5 | 5.6 | 6.06.6 | 6.7 | 6.8 | 7.0 | 7.17.16 | 7.17 | 8.0{minor-version}
| 5.05.5 | {yes-icon} | {yes-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon}
| 5.6 | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon}
| 6.06.6 | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon}
| 6.7 | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon} | {no-icon} | {no-icon}
| 6.8 | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon}
| 7.0 | {no-icon} | {no-icon} | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon}
| 7.17.16 | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon}
| 7.17 | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon}
| 8.0{minor-version} | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {yes-icon} | {yes-icon}
|====
ifeval::["{release-state}"!="released"]
NOTE: This documentation is for {es} version {version}, which is not yet
released. The above compatibility table applies if both clusters are running a
released version of {es}, or if one of the clusters is running a released
version and the other is running a pre-release build with a later build date. A
cluster running a pre-release build of {es} can also communicate with remote
clusters running the same pre-release build. Running a mix of pre-release
builds is unsupported and typically will not work, even if the builds have the
same version number.
endif::[]
// end::remote-cluster-compatibility-matrix[]