Transport profiles do not inherit default transport settings

[ppf2]

Transport profiles do not inherit default transport settings. This PR clarifies the documentation. Please back port accordingly.

Related: #39960

[elasticmachine]

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

[elasticsearchmachine]

@ppf2 please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation.

[elasticsearchmachine]

Pinging @elastic/es-security (Team:Security)

[abdonpijpelink]

@elasticmachine retest this please

[ywangd]

The xpack.security.transport.ssl.enabled setting is an exception:

1. It controls whether SSL is enabled for both the default transport and any transport profiles.
2. Transport profiles do not have a corresponding setting for it.

[leemthompo]

Important

Elastic documentation is migrating to Markdown for version 9.0+. See the migration guide for details.

ℹ️ What's happening?

• Starting January 29, we will start closing all unmerged documentation PRs targeting main/master
• We're migrating from AsciiDoc to Markdown for 9.0+
• 9.0 docs will be frozen from January 29 until February 20 2024
• NOTE: PRs that include both code and documentation changes will remain open

What do I need to do?

For <=8.x docs:

1. Rebase your PR to target the relevant 8.x branch instead
2. The content can remain in AsciiDoc format

For 9.0+ docs:

Option 1:

• Draft docs in Markdown
• Once migration freeze ends, find the relevant page in the new docs system and use the edit options to submit your changes

Option 2:

• Open an issue in elastic/docs-content

💡 Need help?

1. For Elasticians: Ask in #docs Slack channel
2. For external contributors: Open an issue in elastic/docs-content