From 4bead877390b5502e3767b6b6d6c87a45ffdb3bd Mon Sep 17 00:00:00 2001 From: Steven Smith Date: Mon, 19 May 2025 14:06:12 -0400 Subject: [PATCH] Updates a few Operator config docs --- modules/on-prem-configuration-overview.adoc | 2 +- modules/operator-components-intro.adoc | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/modules/on-prem-configuration-overview.adoc b/modules/on-prem-configuration-overview.adoc index ff08b38da..1bc0dfdb1 100644 --- a/modules/on-prem-configuration-overview.adoc +++ b/modules/on-prem-configuration-overview.adoc @@ -15,4 +15,4 @@ This chapter provides an overview of the following concepts: * The minimal required configuration fields. * How to edit and manage your configuration after deployment. -This section applies specifically to on premise {productname} deployment types. For information about configuring {productname-ocp}, see. . . \ No newline at end of file +This section applies specifically to on premise {productname} deployment types. For information about configuring {productname-ocp}, see "{productname-ocp} configuration overview". \ No newline at end of file diff --git a/modules/operator-components-intro.adoc b/modules/operator-components-intro.adoc index 7c92081ea..429f5f05e 100644 --- a/modules/operator-components-intro.adoc +++ b/modules/operator-components-intro.adoc @@ -1,6 +1,6 @@ :_content-type: CONCEPT [id="operator-components-intro"] -= {productname} Operator configuration overview += {productname-ocp} configuration overview When deploying {productname} using the Operator on {ocp}, configuration is managed declaratively through the `QuayRegistry` custom resource (CR). This model allows cluster administrators to define the desired state of the {productname} deployment, including which components are enabled, storage backends, SSL/TLS configuration, and other core features. @@ -8,4 +8,4 @@ After deploying {productname-ocp} with the Operator, administrators can further The Operator reconciles the state defined in the `QuayRegistry` CR and its associated configuration, automatically deploying or updating registry components as needed. -This guide covers the basic concepts behind the `QuayRegistry` CR and modifying your `config.yaml` file on {productname-ocp} deployments. More advanced topics, such as using unmanaged components within the `QuayRegistry` CR, can be found in link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html-single/deploying_the_red_hat_quay_operator_on_openshift_container_platform/index[Deploying {productname} Operator on {ocp}]. \ No newline at end of file +This guide covers the basic concepts behind the `QuayRegistry` CR and modifying your `config.yaml` file on {productname-ocp} deployments. More advanced topics, such as using unmanaged components within the `QuayRegistry` CR, can be found in link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/deploying_the_red_hat_quay_operator_on_openshift_container_platform/index[Deploying {productname} Operator on {ocp}]. \ No newline at end of file