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

secured-routes:removes redundant unused file

This commit is contained in:
JoeAldinger
2025-12-16 13:18:50 -05:00
committed by openshift-cherrypick-robot
parent 3c3021fc2a
commit 9c638cb83e

View File

@@ -1,32 +0,0 @@
:_mod-docs-content-type: ASSEMBLY
[id="configuring-default-certificate"]
= Secured routes
include::_attributes/common-attributes.adoc[]
include::_attributes/attributes-openshift-dedicated.adoc[]
:context: secured-routes
toc::[]
Secure routes provide the ability to use several types of TLS termination to serve certificates to the client. The following sections describe how to create re-encrypt, edge, and passthrough routes with custom certificates.
ifndef::openshift-rosa,openshift-rosa-hcp[]
[IMPORTANT]
====
If you create routes in Microsoft Azure through public endpoints, the resource names are subject to restriction. You cannot create resources that use certain terms. For a list of terms that Azure restricts, see link:https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-reserved-resource-name[Resolve reserved resource name errors] in the Azure documentation.
====
endif::openshift-rosa,openshift-rosa-hcp[]
include::modules/nw-ingress-creating-a-reencrypt-route-with-a-custom-certificate.adoc[leveloffset=+1]
include::modules/nw-ingress-creating-an-edge-route-with-a-custom-certificate.adoc[leveloffset=+1]
include::modules/nw-ingress-creating-a-passthrough-route.adoc[leveloffset=+1]
include::modules/nw-ingress-route-secret-load-external-cert.adoc[leveloffset=+1]
ifndef::openshift-rosa-hcp,openshift-rosa,openshift-dedicated[]
[role="_additional-resources"]
.Additional resources
* xref:../../../support/troubleshooting/investigating-pod-issues.adoc#investigating-pod-issues[Investigating pod issues]
endif::openshift-rosa-hcp,openshift-rosa,openshift-dedicated[]