Remote clusters client settings moved from docs-content

[eedugon]

Solves elastic/docs-content#579

I've added some small improvements:

• Introduction and link to the remote cluster server interface settings that are available in a different doc (network settings)-
• Small intro in the network settings sub-section to also link to the remote cluster settings.

TBD:

• The mapped_page is the same as the one in docs-content, we need to clarify that before merging.
• Review and look for certain new settings that I believe are missing.
• Should we link from the remote cluster settings new document to the remote clusters narrative doc in docs-content? Or just the other way around?

cc: @shainaraskas

[github-actions]

🔍 Preview links for changed docs

• docs/reference/elasticsearch/configuration-reference/remote-clusters.md
• docs/reference/elasticsearch/configuration-reference/networking-settings.md

[github-actions]

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

• Check out the cumulative docs guidelines
• Reach out in the #docs Slack channel

[elasticsearchmachine]

Pinging @elastic/core-docs (Team:Docs)

[shainaraskas]

I'd double check the applies tags before merging. otherwise good

The mapped_page is the same as the one in docs-content, we need to clarify that before merging.

^ this is what we want. it controls backlinks into the old docs

Review and look for certain new settings that I believe are missing.

😍

Should we link from the remote cluster settings new document to the remote clusters narrative doc in docs-content? Or just the other way around?

yes, both, always. links always!

[shainaraskas]

this page has the following front matter:

---
mapped_pages:
  - https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html
applies_to:
  deployment:
    ess:
    self:
---

I think the applies_to is wrong here (it either needs more or less)

without cross-referencing with the tutorials I am not sure which one

[eedugon]

Not totally sure how to address it. This doc is interesting because 80% of the settings are probably valid only for self-managed, but certain settings will definitely be available in ECK, ECE, and ECH.

For the moment I've left:

applies_to:
  deployment:
    ess:
    self:
    ece:
    eck:
  serverless: unavailable

And if you believe we should highlight anything in the text we can do it also, but I don't want the doc to feel overwhelming. Also it's not in the scope of this PR to analyze each setting and apply badges.

[eedugon]

forgot to ping you there @shainaraskas .
Let me know how you would like to address this.... ideally we should clarify the availability of each setting or each section, but all network settings are not in the scope of this PR.

Would you prefer to update the applies_to in the way I've done or would you prefer to keep the previous values?

[shainaraskas]

just switch it to stack if all of the stack deployment types are in scope

similar to https://www.elastic.co/docs/reference/elasticsearch/configuration-reference/data-stream-lifecycle-settings

[shainaraskas]

we'll need to refine this setting-by-setting but you're correct it's out of scope for this pr