Skip to content

Conversation

eedugon
Copy link
Contributor

@eedugon eedugon commented Oct 3, 2025

I've updated the ECE and ECH docs to migrate from the legacy / removed CCS template to a standard template, as the dedicated template is no longer needed anymore.

@shainaraskas : For the ECE doc we have to take a decision, as the doc is NOT applicable to ECE 4.x at all.
I've added a note explaining that the doc is only valid for ECE 3.x installations running deployments in versions earlier than 8.0 with the mentioned template.

The reason of not being applicable is that before upgrading to ECE 4.x all deployments must be on 8.x, and to upgrade to 8.x this template must be not used by any deployment.

Our options are:

  • Accept my changes and leave the doc in our docs V3.
  • Remove the doc entirely and rely on the older version of the doc (ECE 3.x).

The doc for ECH is valid because in ECH we are still supporting 7.17 deployments and "maybe" this removed template, not sure about that.

PS - I have removed the deprecated statement as if the template is removed from the system that implies a previous deprecation.

Copy link

github-actions bot commented Oct 3, 2025

@shainaraskas
Copy link
Collaborator

I THINK the ece doc is ok to delete.

I think the most common entrypoint for this doc is a link from the UI and it comes with a message:

Cross-cluster search and replication are now available for all deployments. As part of this change, we are deprecating dedicated cross-cluster search deployments. You can continue using your deployment, however, we recommend migrating to a different template as soon as possible since you will be required to migrate before upgrading to the next Elastic Stack 8.0 major version. Use the following {docLink}

so I expect the flow would be

  1. upgrade to stack 8.x on ece 3.8 (message appears)
  2. upgrade to ece 4.x

argument against this would be that maybe this is exactly the type of thing that would be good to expose in the 7.17 migration instructions? given that you've been thinking a little about what those would look like I'll let you make the final call.

Copy link
Collaborator

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

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

approved so you can make a choice to keep or get rid of this doc, considering the 7.17 sunset

note: if you do delete it, we'll need to ask the web team to redirect this url to 3.8 (instead of these docs), and remove the listing from https://github.com/elastic/docs/blob/master/resources/asciidoctor/lib/chunker/v3-mapping.json

This guide only applies to {{ece}} 3.x installations and to deployments on {{stack}} versions earlier than 8.0 that were created using the legacy cross-cluster search template.
::::

In order to migrate your existing CCS deployment using the CCS deployment template to the new mechanism which supports CCR and cross-environment remote clusters you will need to migrate your data a new deployment [following these steps](#ece-migrate-ccs-deployment-using-snapshot).
Copy link
Collaborator

Choose a reason for hiding this comment

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

this anchor linking down to the next line is not a great pattern. just say "follow these instructions to ..." (implying content is to follow)

@eedugon
Copy link
Contributor Author

eedugon commented Oct 6, 2025

@kunisen , I'd like to get your thoughts here (for the ECE doc):

Do you think it's beneficial to keep this doc in the new system? https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3312/deploy-manage/remote-clusters/ece-migrate-ccs

Or would it be enough to leave the 3.8 doc as the reference? https://www.elastic.co/guide/en/cloud-enterprise/3.8/ece-migrate-ccs.html

The reason is that the doc is not applicable to ECE 4.x, as before upgrading to ECE 4.x all deployments should have been upgraded to 8.x, and that would imply to get rid of the ccs deployment template.

I don't have a clear opinion here, I'm ok removing the doc because it's probably not needed, but I'm ok leaving it also.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants