Skip to content

[D&M] Remote clusters cleanup #443

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.

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

Merged
merged 23 commits into from
Feb 25, 2025

Conversation

florent-leborgne
Copy link
Contributor

@florent-leborgne florent-leborgne commented Feb 13, 2025

^^

  • There's room for merging more things together later but this does a minimal cleanup and alignment between what the various files say.
  • Also moved API key tabs to display 1st because the Certificate model is deprecated
  • Cleaned up references to Elasticsearch service, some became ecloud, some became ech
  • I intentionally left mentions of some things that are pre-9.0 because in a cloud context, users can still run older versions of the stack, and if we remove them, they'll be documented nowhere since the cloud docs are unversionned.
  • Might have to revisit applies tags once we have the final implementation in hands

Closes: https://github.com/elastic/docs-projects/issues/345

@florent-leborgne florent-leborgne changed the title [D&M] Remote clusters [D&M] Remote clusters cleanup Feb 13, 2025
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.

thanks for doing this. I think it makes sense as an MVP. put an issue in to investigate further restructuring opportunities because this content is super repetitive.

couple things:

  • small formatting errors
  • referencing stack versions without specifying they're stack
  • some stuff I don't remember now

generally I commented on the first I found, but because these pages are mirroring each other the issues exist in multiple places

Copy link
Collaborator

Choose a reason for hiding this comment

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

a perfect page????

Copy link
Collaborator

@shainaraskas shainaraskas Feb 24, 2025

Choose a reason for hiding this comment

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

need to move this page to the reference

edit: #579

shainaraskas
shainaraskas previously approved these changes Feb 24, 2025
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.

works for me!

mapped_pages:
- https://www.elastic.co/guide/en/cloud/current/ec-enable-ccs-for-eck.html
---

# Remote clusters between {{ech}} and ECK [ec-enable-ccs-for-eck]

These steps describe how to configure remote clusters between an {{es}} cluster in {{ech}} and an {{es}} cluster running within [{{eck}} (ECK)](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-overview.html). Once that’s done, you’ll be able to [run CCS queries from {{es}}](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-cross-cluster-search.html) or [set up CCR](https://www.elastic.co/guide/en/elasticsearch/reference/current/ccr-getting-started-tutorial.html).
These steps describe how to configure remote clusters between an {{es}} cluster in {{ech}} and an {{es}} cluster running within [{{eck}} (ECK)](/deploy-manage/deploy/cloud-on-k8s.md). Once that’s done, you’ll be able to [run CCS queries from {{es}}](/solutions/search/cross-cluster-search.md) or [set up CCR](/deploy-manage/tools/cross-cluster-replication/set-up-cross-cluster-replication.md).


## Establish trust between two clusters [ec_establish_trust_between_two_clusters]
Copy link
Collaborator

@shainaraskas shainaraskas Feb 24, 2025

Choose a reason for hiding this comment

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

line 81: confused about what the user is supposed to do on the target page. the establishing trust procedures above also refer to these pages.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If that's what you're referring to: Those page used to be maintained by the ECK team. Only thing I know is that doing it on ECK is very close to how it's done with self-managed, which isn't very concrete information... We can make a note to improve this later.

Copy link
Contributor

@lcawl lcawl left a comment

Choose a reason for hiding this comment

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

🚀

@florent-leborgne florent-leborgne enabled auto-merge (squash) February 25, 2025 09:24
@florent-leborgne florent-leborgne merged commit 86c3dd0 into elastic:main Feb 25, 2025
4 checks passed
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.

3 participants