remote-clusters-shared.asciidoc 2.1 KB

12345678910111213141516171819202122232425262728
  1. // tag::remote-cluster-compatibility-matrix[]
  2. [cols="^,^,^,^,^,^,^,^,^,^"]
  3. |====
  4. | 9+^h| Local cluster
  5. h| Remote cluster | 5.0–5.5 | 5.6 | 6.0–6.6 | 6.7 | 6.8 | 7.0 | 7.1–7.16 | 7.17 | 8.0–{minor-version}
  6. | 5.0–5.5 | {yes-icon} | {yes-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon}
  7. | 5.6 | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon}
  8. | 6.0–6.6 | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon}
  9. | 6.7 | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon} | {no-icon} | {no-icon}
  10. | 6.8 | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon}
  11. | 7.0 | {no-icon} | {no-icon} | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon}
  12. | 7.1–7.16 | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {no-icon}
  13. | 7.17 | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon} | {yes-icon}
  14. | 8.0–{minor-version} | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {no-icon} | {yes-icon} | {yes-icon}
  15. |====
  16. ifeval::["{release-state}"!="released"]
  17. NOTE: This documentation is for {es} version {version}, which is not yet
  18. released. The above compatibility table applies if both clusters are running a
  19. released version of {es}, or if one of the clusters is running a released
  20. version and the other is running a pre-release build with a later build date. A
  21. cluster running a pre-release build of {es} can also communicate with remote
  22. clusters running the same pre-release build. Running a mix of pre-release
  23. builds is unsupported and typically will not work, even if the builds have the
  24. same version number.
  25. endif::[]
  26. // end::remote-cluster-compatibility-matrix[]