K8s: add let's encrypt limitation to cert-manager page#3472
Merged
Conversation
Contributor
🛡️ Jit Security Scan Results
✅ No security findings were detected in this PR
Security scan by Jit
|
heinrich-redislabs
left a comment
heinrich-redislabs
left a comment
There was a problem hiding this comment.
Added a comment explaining what is the problem that users will have to understand if the cert-manager does not populate the ca.crt field with their specific certificate issuer.
heinrich-redislabs
approved these changes
Jun 11, 2026
EliShteinman
added a commit
to EliShteinman/docs
that referenced
this pull request
Jun 11, 2026
Documents a Let's Encrypt limitation on the cert-manager docs page.
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
3 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.
DOC-6737
Note
Low Risk
Documentation-only edits with no runtime, security, or application code changes.
Overview
Updates the Use production certificate authorities section on the Kubernetes cert-manager docs (versioned and default paths) so ACME/Let’s Encrypt is no longer presented as a plug-and-play setup.
The Let’s Encrypt subsection is renamed to Let’s Encrypt and ACME issuers and the sample
ClusterIssuer/CertificateYAML is removed. The text now states that ACME issuers typically leaveca.crtwithout the root CA, so cert-manager secrets may lack the full chain Redis Software needs, and documents a three-step workaround: build the full chain, store it in a Kubernetes secret, and point the Redis custom resource at that secret instead of the cert-manager-generated one. A note generalizes this to any issuer that omits the root inca.crt, and a short contrast clarifies that private CA or Vault paths that supply the full chain need no extra steps.Reviewed by Cursor Bugbot for commit e57cfb9. Bugbot is set up for automated code reviews on this repo. Configure here.