[codex] Clarify private CA requirements for self-hosted Wave#1276
Draft
llewellyn-sl wants to merge 1 commit intomasterfrom
Draft
[codex] Clarify private CA requirements for self-hosted Wave#1276llewellyn-sl wants to merge 1 commit intomasterfrom
llewellyn-sl wants to merge 1 commit intomasterfrom
Conversation
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
gavinelder
reviewed
Apr 9, 2026
Contributor
gavinelder
left a comment
gavinelder
left a comment
There was a problem hiding this comment.
Could this be moved to a single page covering all apps under advanced topics ?
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.
Summary
This draft clarifies how private CA certificates must be applied when Platform is deployed with self-hosted Wave.
Source context
Repo and doc targets
seqeralabs/docsplatform-enterprise_versioned_docsversion-25.3/enterprise/configuration/ssl_tls.mdversion-25.3/enterprise/configuration/wave.mdRationale
The new ticket update added installer-level guidance that was missing from the current docs: when a deployment uses self-hosted Wave with private CA material, the same CA root certificate has to be available beyond the base Platform services. The existing SSL/TLS and Wave pages were the smallest high-value place to make that explicit.
What changed
backend,cron, and Wave containers.Validation
npx markdownlint-cli2on the two touched files.ssl_tls.md; no new automated build was run.Follow-up
Please confirm whether the final installer implementation wants stricter language around reverse proxy certificate handling.