-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the documentation about importing external certificates #1598
Update the documentation about importing external certificates #1598
Conversation
@@ -1,92 +1,174 @@ | |||
|
|||
|
|||
[id="importing-tls-certificates-to-{prod-id-short}-server-java-trustore_{context}"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also update the id
and all xref
statements pointing to this id
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
---- | ||
+ | ||
- Certificates are mounted in folder `/public-certs/` of the {prod-short} server container. This command returns the list of files in that folder: | ||
- {prod-short} mounts certificates in folder `/public-certs/` of the {prod-short} server container. This command returns the list of files in that folder: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that checking /public-certs folder is not enough.
when ca-certs
configmap is updated then k8s automatically refreshes /public-certs
.
but those certificates won't be added to java trust store of the che-server and keycloak.
It seems this procedure is turning into a collection of 2 distinct procedures depending on the method used to install the Che instance. We have a similar case Upgrading Che. We make there the distinction between these 2 deployment flows: using OperatorHub vs. using the CLI management tool. For consistency purposes, using the same presentation here would be awesome, but is it relevant? |
...stallation-guide/partials/proc_importing-tls-certificates-to-che-server-java-truststore.adoc
Outdated
Show resolved
Hide resolved
...stallation-guide/partials/proc_importing-tls-certificates-to-che-server-java-truststore.adoc
Outdated
Show resolved
Hide resolved
...stallation-guide/partials/proc_importing-tls-certificates-to-che-server-java-truststore.adoc
Outdated
Show resolved
Hide resolved
...stallation-guide/partials/proc_importing-tls-certificates-to-che-server-java-truststore.adoc
Outdated
Show resolved
Hide resolved
according to whether the certificates are added; - at installation time - on an already-running installation.
aa64568
to
49b4702
Compare
@themr0c I don't know why the vale tests fail during CI while I have no vale error on my file in the Che workspace. Maybe rules have changed ? @l0rd Since the PR comes from my fork, the result automatically pushed on netlify is not the right one. |
In fact we thought if would be more beneficial to split the documentation into 2 sub-section according to the use-case:
So I assume we would not also split according to the underlying installation method (operator or helm). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The document is much clearer now. Good job @davidfestal. But there are still some points to review.
modules/installation-guide/partials/proc_importing-external-or-additional-tls-certificates.adoc
Outdated
Show resolved
Hide resolved
modules/installation-guide/partials/proc_importing-external-or-additional-tls-certificates.adoc
Outdated
Show resolved
Hide resolved
modules/installation-guide/partials/proc_importing-external-or-additional-tls-certificates.adoc
Outdated
Show resolved
Hide resolved
modules/installation-guide/partials/proc_importing-external-or-additional-tls-certificates.adoc
Outdated
Show resolved
Hide resolved
* {prod-short} already uses some reserved file names to automatically inject certificates into the ConfigMap, so you should avoid using the following reserved file names to save your certificates: | ||
** `ca-bundle.crt` | ||
** `ca.crt` | ||
==== |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The paragraph above is repeated multiple times in this article. Can we move it to a different doc component and reference it multiple times?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in commit 3f481ae
modules/installation-guide/partials/proc_importing-external-or-additional-tls-certificates.adoc
Outdated
Show resolved
Hide resolved
modules/installation-guide/partials/proc_importing-external-or-additional-tls-certificates.adoc
Outdated
Show resolved
Hide resolved
modules/installation-guide/partials/proc_importing-external-or-additional-tls-certificates.adoc
Outdated
Show resolved
Hide resolved
modules/installation-guide/partials/proc_importing-external-or-additional-tls-certificates.adoc
Outdated
Show resolved
Hide resolved
modules/installation-guide/partials/proc_importing-external-or-additional-tls-certificates.adoc
Outdated
Show resolved
Hide resolved
@davidfestal Any chance you can include the proposed changes and rebase soon? |
I'll try to work on it tomorrow |
Co-authored-by: Mario Loriedo <mario.loriedo@gmail.com>
Co-authored-by: Mario Loriedo <mario.loriedo@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM Great job @davidfestal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* First changes * Split the procedure into 2 sections according to whether the certificates are added: - at installation time - on an already-running installation. * Add changes proposed by @l0rd * Change the title according to @l0rd review comment * Fix comment #1598 (review) * Add verification steps at the workspace level * Fix some of the vale errors Co-authored-by: Mario Loriedo <mario.loriedo@gmail.com> Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
* First changes * Split the procedure into 2 sections according to whether the certificates are added: - at installation time - on an already-running installation. * Add changes proposed by @l0rd * Change the title according to @l0rd review comment * Fix comment #1598 (review) * Add verification steps at the workspace level * Fix some of the vale errors Co-authored-by: Mario Loriedo <mario.loriedo@gmail.com> Co-authored-by: Yana Hontyk <yhontyk@redhat.com>
What does this PR do?
This PR Updates the documentation about importing additional certificates in a Ce installation, to reflect the current status of Che on this Topic.
What issues does this PR fix or reference?
This PR refers to issue https://issues.redhat.com/browse/RHDEVDOCS-2089
Specify the version of the product this PR applies to.
This PR applies to the last Upstream release (7.18.2) and to the 2.4 downstream release.
PR Checklist
As the author of this Pull Request I made sure that:
vale
has been run successfully against the PR branch