Skip to content

ECK Kibana secure settings and encryption refinement#6429

Open
eedugon wants to merge 4 commits into
mainfrom
eck_kibana_secure_settings
Open

ECK Kibana secure settings and encryption refinement#6429
eedugon wants to merge 4 commits into
mainfrom
eck_kibana_secure_settings

Conversation

@eedugon
Copy link
Copy Markdown
Contributor

@eedugon eedugon commented May 12, 2026

Summary

Closes #4096

ECK handles automatically certain settings and this wasn't properly showed to the users, except in the "scale out Kibana" section.

This PR aims to integrate this information better within the ECK docs.

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes --> Cursor + GPT 5.3
  • No

@github-actions
Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 12, 2026

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 12, 2026

✅ Vale Linting Results

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

@eedugon eedugon changed the title initial changes ECK Kibana secure settings and encryption refinement May 12, 2026
@eedugon eedugon marked this pull request as ready for review May 12, 2026 10:23
@eedugon eedugon requested a review from a team as a code owner May 12, 2026 10:23
```

:::{warning}
Always ensure the setting is listed in the [configuration reference](kibana://reference/configuration-reference.md) and that the value you provide matches the expected format before adding it to the keystore. Invalid, unsupported, or incorrect settings cause {{kib}} to fail to start.
Copy link
Copy Markdown
Member

@yetanothertw yetanothertw May 12, 2026

Choose a reason for hiding this comment

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

I think there's a typo here in the last sentence to fail to start. Or it just reads odd.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Maybe something like:

Suggested change
Always ensure the setting is listed in the [configuration reference](kibana://reference/configuration-reference.md) and that the value you provide matches the expected format before adding it to the keystore. Invalid, unsupported, or incorrect settings cause {{kib}} to fail to start.
Always ensure the setting is listed in the [configuration reference](kibana://reference/configuration-reference.md) and that the value you provide matches the expected format before adding it to the keystore. Specifying invalid, unsupported, or incorrect settings will prevent {{kib}} from starting successfully.

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.

[Internal]: Cross-reference Kibana secure settings docs for ECK

2 participants