Browse Source

Reinstate prerelease upgrade warning (#90093)

This warning was lost in #83489, but it's important we have it in these
docs since users keep on trying this kind of invalid upgrade. This
commit reinstates the lost warning.
David Turner 3 years ago
parent
commit
c7da07068c
1 changed files with 10 additions and 0 deletions
  1. 10 0
      docs/reference/upgrade.asciidoc

+ 10 - 0
docs/reference/upgrade.asciidoc

@@ -1,6 +1,16 @@
 [[setup-upgrade]]
 = Upgrade {es}
 
+ifeval::["{release-state}"!="released"]
+[[upgrade-pre-release]]
+IMPORTANT: This documentation is for {es} {version}, which is not yet released.
+You can upgrade from a previously released version to a pre-release build, if
+following a supported upgrade path. Upgrading from a pre-release build to any
+other build is not supported, and can result in errors or silent data loss. If
+you run a pre-release build for testing, discard the contents of the cluster
+before upgrading to another build of {es}.
+endif::[]
+
 {es} clusters can usually be upgraded one node at a time so upgrading does not
 interrupt service. For upgrade instructions, refer to
 {stack-ref}/upgrading-elastic-stack.html[Upgrading to Elastic {version}].