K8s: add let's encrypt limitation to cert-manager page#3472
Open
kaitlynmichael wants to merge 1 commit into
Open
K8s: add let's encrypt limitation to cert-manager page#3472kaitlynmichael wants to merge 1 commit into
kaitlynmichael wants to merge 1 commit into
Conversation
Contributor
🛡️ Jit Security Scan Results
✅ No security findings were detected in this PR
Security scan by Jit
|
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.
DOC-6737
Note
Low Risk
Documentation-only changes to cert-manager guidance; no runtime or security code paths modified.
Overview
Documents that Let's Encrypt and other ACME cert-manager issuers are not supported for the Redis Enterprise Kubernetes cert-manager integration, and steers readers toward issuers that supply a full chain (private CA, Vault).
The benefits list no longer mentions Let's Encrypt; it now stresses issuers that provide the root CA certificate. The former Let's Encrypt setup examples are removed and replaced with a warning: ACME issuers typically omit
ca.crtin TLS secrets, while Redis Software needs the root CA to build trust—a product limitation, not Kubernetes-specific. Production guidance now points to private CA or Vault. Troubleshooting drops ACME-only bullets (DNS validation, Let's Encrypt rate limits).The same edits apply to
cert-manager.mdunder both the versioned (8.0.18) and unversioned Kubernetes security docs.Reviewed by Cursor Bugbot for commit bc59224. Bugbot is set up for automated code reviews on this repo. Configure here.