openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

For OCPBUGS-45035: Fixed the hyperlink and made statement consistency under the security section

Browse Source
This commit is contained in:
Bhushan Jahagirdar
2025-11-27 15:32:48 +05:30
committed by openshift-cherrypick-robot
parent 2bab6ac037
commit 78f636980d
4 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
security/certificate_types_descriptions/ingress-certificates.adoc
View File

@@ -83,7 +83,7 @@ Ingress to the cluster via a secured route uses the default certificate of the I
== Management
Ingress certificates are managed by the user. See xref:../../security/certificates/replacing-default-ingress-certificate.adoc#replacing-default-ingress[Replacing the default ingress certificate] for more information.
Ingress certificates are managed by the user. For more information, see xref:../../security/certificates/replacing-default-ingress-certificate.adoc#replacing-default-ingress[Replacing the default ingress certificate] .
== Renewal

2
security/certificate_types_descriptions/monitoring-and-cluster-logging-operator-component-certificates.adoc
View File

@@ -10,7 +10,7 @@ toc::[]
Monitoring components secure their traffic with service CA certificates. These certificates are valid for 2 years and are replaced automatically on rotation of the service CA, which is every 13 months.
If the certificate lives in the `openshift-monitoring` or `openshift-logging` namespace, it is system managed and rotated automatically.
If the certificate is present in the `openshift-monitoring` or `openshift-logging` namespace, it is system managed and rotated automatically.
== Management

2
security/certificate_types_descriptions/olm-certificates.adoc
View File

@@ -12,7 +12,7 @@ All certificates for Operator Lifecycle Manager (OLM) components (`olm-operator`
When installing Operators that include webhooks or API services in their `ClusterServiceVersion` (CSV) object, OLM creates and rotates the certificates for these resources. Certificates for resources in the `openshift-operator-lifecycle-manager` namespace are managed by OLM.
OLM will not update the certificates of Operators that it manages in proxy environments. These certificates must be managed by the user using the subscription config.
OLM does not update the certificates of Operators that it manages in proxy environments. These certificates must be managed by the user using the subscription config.
[role="_additional-resources"]
.Next steps

2
security/certificate_types_descriptions/proxy-certificates.adoc
View File

@@ -64,7 +64,7 @@ The user-provided trust bundle is represented as a config map. The config map is
Complete proxy support means connecting to the specified proxy and trusting any signatures it has generated. Therefore, it is necessary to let the user specify a trusted root, such that any certificate chain connected to that trusted root is also trusted.
If you use the {op-system} trust bundle, place CA certificates in `/etc/pki/ca-trust/source/anchors`. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/securing_networks/using-shared-system-certificates_securing-networks[Using shared system certificates] in the {op-system-base-full} _Securing networks_ document.
If you use the {op-system} trust bundle, place CA certificates in `/etc/pki/ca-trust/source/anchors`. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/securing_networks/using-shared-system-certificates[Using shared system certificates] in the {op-system-base-full} _Securing networks_ document.
== Expiration