Skip to content

ECH available stack versions statements updated #4607

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

Open
eedugon wants to merge 2 commits into
base: main
Choose a base branch
from
Open

ECH available stack versions statements updated #4607

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e1e3338
ech available versions statements updated
eedugon Jan 13, 2026
5efbac1
ech available versions statements updated
eedugon Jan 13, 2026
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
12 changes: 10 additions & 2 deletions deploy-manage/deploy/elastic-cloud/available-stack-versions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,10 +22,18 @@

## Available {{stack}} versions [ec-version-policy-available]

{{stack}} uses a versions code that is constructed of three numbers separated by dots: the leftmost number is the number of the major release, the middle number is the number of the minor release and the rightmost number is the number of the maintenance release (e.g., 8.3.2 means major release 8, minor release 3 and maintenance release 2).
{{stack}} uses a version numbering scheme based on three numbers separated by dots. The leftmost number indicates the major release, the middle number indicates the minor release, and the rightmost number indicates the maintenance release. For example, `8.3.2` represents major release 8, minor release 3, and maintenance release 2.

You might sometimes notice additional versions listed in the user interface beyond the versions we currently support and maintain, such as [release candidate builds](#ec-release-builds) and older versions. If a version is listed in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), it can be deployed.
In {{ech}}, not all [{{stack}} versions](https://www.elastic.co/support/eol) are available for deploying. By default, the following versions are available in the UI:
Copy link
Contributor

@jakommo jakommo Jan 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In {{ech}}, not all [{{stack}} versions](https://www.elastic.co/support/eol) are available for deploying. By default, the following versions are available in the UI:
By default, the following versions are available in the {{ech}} UI:

Trying to make this sound more positive (the "not all stack versions are available" has a bit of a negative touch IMHO) but free free to reword or disregard this suggestion.


* The two latest minor versions of the latest major version
* The latest minor version of the previous major version

For example, if the latest {{stack}} version is {{version.stack}}, {{ech}} makes the following versions available:
* {{version.stack | M.M }} and {{version.stack | M.M+1 | M.M }}
* 8.19

Additional versions can appear in the UI, such as [release candidate builds](#ec-release-builds) or older versions. If a version is listed in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), it can be deployed.

Check notice on line 36 in deploy-manage/deploy/elastic-cloud/available-stack-versions.md

View workflow job for this annotation

GitHub Actions / preview / vale 

Elastic.Versions: Use 'or earlier' instead of 'or older' when referring to versions.
Copy link
Contributor

@jakommo jakommo Jan 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Additional versions can appear in the UI, such as [release candidate builds](#ec-release-builds) or older versions. If a version is listed in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), it can be deployed.
Additional versions can appear in the UI, such as [release candidate builds](#ec-release-builds) or older versions that you have a running deployment on. If a version is listed in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), it can be deployed.

There might be better ways to say thif, but basically if you run a non-EOL version that doesn't match the definition in https://github.com/elastic/docs-content/pull/4607/changes#diff-6f210dc543344c05d32b32b3e89f7efa7fbccb88e4bc6baeabd1394ff341ced2R29-R30 they will also show up as available version to allow spinning up a clone to test upgrades etc.

Copy link
Contributor

@jakommo jakommo Jan 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we also add a link to https://www.elastic.co/docs/reference/cloud/cloud-hosted/ec-api-deployment-crud#ec_using_the_api_to_create_deployment_with_non_eol_versions and say that any non-EOL version can be deployed via API?

Copy link
Contributor Author

@eedugon eedugon Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great point @jakommo , I'll find a way to include your first statement properly, so users understand that they will also have available their "currently used" versions as long as they are supported.

About your second question:

Should we also add a link to https://www.elastic.co/docs/reference/cloud/cloud-hosted/ec-api-deployment-crud#ec_using_the_api_to_create_deployment_with_non_eol_versions and say that any non-EOL version can be deployed via API?

That's your & PM decision I'd say. I don't have any strong opinion. Considering your background and experience in this area, I'd do whatever you suggest, or if you prefer to double check with a PM that's totally ok too.

Copy link
Contributor

@jakommo jakommo Jan 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd say let's add a link to the API instructions. It's already in the public docs and if a user reaches out to support we well them the same, so I see no reason to "hide" this.


## New {{stack}} versions [ec-version-policy-new]

Expand Down
Loading