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

Removed tech preview for support router load secrets

Browse Source
This commit is contained in:
subhtk
2025-04-30 19:22:42 +05:30
committed by openshift-cherrypick-robot
parent 96b7667e2e
commit d39e12e833
2 changed files with 1 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
modules/nw-ingress-route-secret-load-external-cert.adoc
View File

@@ -6,9 +6,6 @@
[id="nw-ingress-route-secret-load-external-cert_{context}"]
= Creating a route with externally managed certificate
:FeatureName: Securing route with external certificates in TLS secrets
include::snippets/technology-preview.adoc[]
You can configure {product-title} routes with third-party certificate management solutions by using the `.spec.tls.externalCertificate` field of the route API. You can reference externally managed TLS certificates via secrets, eliminating the need for manual certificate management. Using the externally managed certificate reduces errors ensuring a smoother rollout of certificate updates, enabling the OpenShift router to serve renewed certificates promptly.
[NOTE]

5
security/cert_manager_operator/cert-manager-securing-routes.adoc
View File

@@ -6,10 +6,7 @@ include::_attributes/common-attributes.adoc[]
toc::[]
In the {product-title}, the route API is extended to provide a configurable option to reference TLS certificates via secrets. With the xref:../../networking/routes/secured-routes.adoc#nw-ingress-route-secret-load-external-cert_secured-routes[Creating a route with externally managed certificate] Technology Preview feature enabled, you can minimize errors from manual intervention, streamline the certificate management process, and enable the {product-title} router to promptly serve the referenced certificate.
:FeatureName: Securing routes with the {cert-manager-operator}
include::snippets/technology-preview.adoc[]
In the {product-title}, the route API is extended to provide a configurable option to reference TLS certificates via secrets. With xref:../../networking/routes/secured-routes.adoc#nw-ingress-route-secret-load-external-cert_secured-routes[externally managed certificates] enabled, you can minimize errors from manual intervention, streamline the certificate management process, and enable the {product-title} router to promptly serve the referenced certificate.
include::modules/cert-manager-configuring-routes.adoc[leveloffset=+1]