Removes SSL module to reference securing quay (quay#1344)

Co-authored-by: Steven Smith <[email protected]>

Author: stevsmit

deploy_red_hat_quay_operator/master.adoc

@@ -2,6 +2,7 @@ include::modules/attributes.adoc[]
 
 [id="deploy-quay-on-openshift-op-tng"]
 = Deploying the {productname} Operator on {ocp}
+:context: quay-operator
 
 {productname} is an enterprise-quality container registry. Use {productname} to build and store container images, then make them available to deploy across your enterprise.
 
@@ -85,8 +86,8 @@ include::modules/operator-config-cli-download.adoc[leveloffset=+2]
 
 //SSL/TLS
 include::modules/operator-custom-ssl-certs-config-bundle.adoc[leveloffset=+1]
-include::modules/ssl-create-certs.adoc[leveloffset=+2]
-include::modules/creating-custom-ssl-certs-config-bundle.adoc[leveloffset=+2]
+//include::modules/ssl-create-certs.adoc[leveloffset=+2]
+//include::modules/creating-custom-ssl-certs-config-bundle.adoc[leveloffset=+2]
 
 //Deploying configuration tool
 //include::modules/operator-config-ui.adoc[leveloffset=+1]
@@ -99,3 +100,5 @@ include::modules/creating-custom-ssl-certs-config-bundle.adoc[leveloffset=+2]
 .Next steps
 
 * https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/red_hat_quay_operator_features/[{productname} features]
+
+*link:https://docs.redhat.com/en/documentation/red_hat_quay/3.14/html/securing_red_hat_quay/index[Securing {productname}]

modules/modifying-config-bundle-secret-cli.adoc

@@ -0,0 +1,17 @@
+:_content-type: CONCEPT
+[id="modifying-configbundlesecret-cli"]
+= Modifying the configuration file by using the CLI
+
+You can modify the `config.yaml` file that is stored by the `configBundleSecret` by using the CLI.
+
+[NOTE]
+====
+Modifying the `config.yaml` file that is stored by the `configBundleSecret` is a multi-step procedure that requires base64 decoding the existing configuration file and then uploading the changes. For most cases, using the {ocp} web console to make changes to the `config.yaml` file is simpler.
+====
+
+.Prerequisites
+
+* You are logged in to the {ocp} cluster as a user with admin privileges. 
+
+.Procedure 
+

modules/operator-custom-ssl-certs-config-bundle.adoc

@@ -2,6 +2,8 @@
 [id="operator-custom-ssl-certs-config-bundle"]
 = Configuring custom SSL/TLS certificates for {productname-ocp}
 
+ifeval::["{context}" == "quay-security"]
+
 When {productname} is deployed on {ocp}, the `tls` component of the `QuayRegistry` custom resource definition (CRD) is set to `managed` by default. As a result, {ocp}'s Certificate Authority is used to create HTTPS endpoints and to rotate SSL/TLS certificates. 
 
 You can configure custom SSL/TLS certificates before or after the initial deployment of {productname-ocp}. This process involves creating or updating the `configBundleSecret` resource within the `QuayRegistry` YAML file to integrate your custom certificates and setting the `tls` component to `unmanaged`. 
@@ -18,4 +20,9 @@ The following procedures enable you to apply custom SSL/TLS certificates to ensu
 * The following procedure is used for securing {productname} with an HTTPS certificate. Note that this differs from managing Certificate Authority Trust Bundles. CA Trust Bundles are used by system processes within the `Quay` container to verify certificates against trusted CAs, and ensure that services like LDAP, storage backend, and OIDC connections are trusted.
 
 * If you are adding the certificates to an existing deployment, you must include the existing `config.yaml` file in the new config bundle secret, even if you are not making any configuration changes.
-====
+====
+endif::[]
+
+ifeval::["{context}" == "quay-operator"]
+This content has been moved to link:https://docs.redhat.com/en/documentation/red_hat_quay/3.14/html/securing_red_hat_quay/index[Securing {productname}]. This chapter will be removed in a future version of {productname}.
+endif::[]

modules/ssl-tls-quay-overview.adoc

@@ -1,6 +1,6 @@
 :_content-type: CONCEPT
 [id="ssl-tls-quay-overview"]
-= SSL and TLS for {productname}
+= Configuring SSL and TLS for {productname}
 
 The Secure Sockets Layer (SSL) protocol was originally developed by Netscape Corporation to provide a mechanism for secure communication over the Internet. Subsequently, the protocol was adopted by the Internet Engineering Task Force (IETF) and renamed to Transport Layer Security (TLS).