docs: add documentation for using custom CA certificates with Jenkins in Docker and Kubernetes - #8928
Conversation
Add comprehensive documentation for importing custom CA certificates in Jenkins Docker containers using secure patterns. Covers three approaches: - Docker Compose with init container - Kubernetes/Helm with init container - Custom Dockerfile with baked-in certificates All approaches maintain security by keeping the system truststore immutable and root-owned.
|
@Piyush0049 same as jenkinsci/docker#2251 (comment), please stop merging master branch in your PRs, no need to run again and again CI. |
|
@dduportal @lemeurherve would it be possible to get some input from you guys on this PR? |
dduportal
left a comment
There was a problem hiding this comment.
The technical content looks good to me!
The only feedback I have would be to be a bit more clear in the title + introduction that this page is only for Custom CA certificates for Jenkins running in containers (e.g. Docker / Kubernetes).
The reason is that it's far from being the main way to run Jenkins and we don't want non Docker/Kubernetes Jenkins admins to land on this page while they use native Linux packages.
@krisstern It also means that you might want to link this page, once merged, from the the Docker / Kubernetes pages if any (I can't recall the exact documentation page tree)
|
@dduportal @krisstern I’ve updated the title and intro to clearly scope this to Jenkins running in Docker/Kubernetes containers only. Please let me know if any further changes are required. |
Co-authored-by: Hervé Le Meur <91831478+lemeurherve@users.noreply.github.com>
Co-authored-by: Hervé Le Meur <91831478+lemeurherve@users.noreply.github.com>
Co-authored-by: Kris Stern <88480540+krisstern@users.noreply.github.com>
@dduportal will do |
|
Congratulations on getting your very first jenkins.io pull request merged 🎉🥳 |
|
Thank you so much for the reviews, guidance, and merge! I learned a lot from this PR and really appreciate everyone’s help. |
|
@Piyush0049 that's good to know. If you are interested you can link this up to both the Docker and Kubernetes documentation, that is the last step to make your work here visible. |
|
Definitely, I’m working on it. |
|
That's great! We appreciate it |
|
I’ve opened a new PR for the follow-up linking changes from the Docker and Kubernetes docs. Please let me know if anything else is needed. |
…ation pages Include the _custom-ca-certificates.adoc partial in both docker.adoc and kubernetes.adoc to make the documentation visible on the website. Follow-up to PR jenkins-infra#8928 as requested by @krisstern and @dduportal
…ation pages (#9200) * docs: include custom CA certificates in Docker and Kubernetes installation pages Include the _custom-ca-certificates.adoc partial in both docker.adoc and kubernetes.adoc to make the documentation visible on the website. Follow-up to PR #8928 as requested by @krisstern and @dduportal * docs: restore original heading title * docs: Shift headings down one level to fix TOC nesting * Revert "docs: Shift headings down one level to fix TOC nesting" This reverts commit c60f079. * docs: update topmost heading to level 3 * docs: shift all subheadings down while keeping main title at level 2
Description
This documentation covers secure ways to add custom CA certificates to Jenkins running in Docker or Kubernetes.
What's Added
Added new documentation page:
content/doc/book/installing/_custom-ca-certificates.adocThis documentation covers three secure approaches for custom CA certificates:
Why This Documentation
This documentation complements security improvements in jenkinsci/docker where we removed the insecure runtime certificate import feature that gave the Jenkins user write access to the system truststore.
Users still need a way to add custom CA certificates for:
This documentation provides secure, tested patterns that maintain the principle of keeping the system truststore immutable and root-owned.
Key Features
✅ Complete working examples for all three approaches
✅ Security-first design - system truststore remains root-owned
✅ Certificate format requirements and conversion examples
✅ Troubleshooting guide for common issues
✅ Security warnings prominently displayed
✅ Links to related resources (Helm charts, Docker images)
Security
All documented approaches maintain security by:
Testing
All examples have been tested and verified:
Related
Checklist