self-signed statements reviewed in ECK http and transport TLS docs#6111
Merged
Conversation
Contributor
🔍 Preview links for changed docs |
Contributor
Vale Linting ResultsSummary: 3 suggestions found 💡 Suggestions (3)
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
commented
Apr 24, 2026
| ``` | ||
|
|
||
| Here is how to issue multiple {{es}} certificates from a single self-signed CA. This is useful for example for [Remote clusters](/deploy-manage/remote-clusters/eck-remote-clusters.md) which need to trust each other’s CA, in order to avoid mounting N CAs when a cluster is connected to N other clusters. | ||
| #### Custom private CA and certificate using cert-manager [k8s_custom_http_ca_using_cert_manager] |
Contributor
Author
There was a problem hiding this comment.
I've added a new header because the example below does not create a self-signed cert (previous header and example), but a CA + cert.
marciw
approved these changes
Apr 27, 2026
Member
marciw
left a comment
marciw
left a comment
There was a problem hiding this comment.
LGTM with one small suggestion
Co-authored-by: Marci W <333176+marciw@users.noreply.github.com>
Contributor
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both the transport and http docs of ECK include some statements about ECK creating self-signed certificates for the instances, where that's not really the case.
ECK now generates a CAs (self-signed of course) for transport and http, and then uses the CAs to issue the required certs for the instances, hence ECK is not using self-signed certs.
Besides that I've added the following small improvements:
isCA: trueto false in one of the manifests for cert-manager, as the objective of the manifest is to create a server cert and not a CA.hulkexamples toquickstart.PS - I strongly believe in the past ECK was probably creating self-signed certs for HTTP by default, because multiple items point to that:
specfeature is calledtls.selfSignedCertificate, even if it's creating a CA + cert.tls.crtfrom the public HTTP secret, which is not useful anymore if that cert is signed by a private ECK-managed CA (a user needs the CA and not the HTTP cert for trusting purposes).