Removes config-editor pod info from docs and updates RNs (#842)

Co-authored-by: Steven Smith <stevsmit@stevsmit.remote.csb>

Author: stevsmit

modules/backing-up-red-hat-quay-operator.adoc

@@ -185,7 +185,6 @@ $ oc get pod
 quay-operator.v3.7.1-6f9d859bd-p5ftc               1/1     Running     0             12m
 quayregistry-clair-postgres-7487f5bd86-xnxpr       1/1     Running     1 (12m ago)   12m
 quayregistry-quay-app-upgrade-xq2v6                0/1     Completed   0             12m
-quayregistry-quay-config-editor-6dfdcfc44f-hlvwm   1/1     Running     0             73s
 quayregistry-quay-database-859d5445ff-cqthr        1/1     Running     0             12m
 quayregistry-quay-redis-84f888776f-hhgms           1/1     Running     0             12m
 ----

modules/config-custom-ssl-certs-kubernetes.adoc

@@ -47,7 +47,7 @@ c1psWGpqeGlPQmNEWkJPMjJ5d0pDemVnR2QNCnRsbW9JdEF4YnFSdVd3PT0KLS0tLS1FTkQgQ0VSVElG
 +
 [source,terminal]
 ----
-$ kubectl delete pod quay-operator.v3.7.1-6f9d859bd-p5ftc quayregistry-clair-postgres-7487f5bd86-xnxpr quayregistry-quay-app-upgrade-xq2v6 quayregistry-quay-config-editor-6dfdcfc44f-hlvwm quayregistry-quay-database-859d5445ff-cqthr quayregistry-quay-redis-84f888776f-hhgms
+$ kubectl delete pod quay-operator.v3.7.1-6f9d859bd-p5ftc quayregistry-clair-postgres-7487f5bd86-xnxpr quayregistry-quay-app-upgrade-xq2v6  quayregistry-quay-database-859d5445ff-cqthr quayregistry-quay-redis-84f888776f-hhgms
 ----
 +
 Afterwards, the {productname} deployment automatically schedules replace pods with the new certificate data. 

modules/config-fields-v2-ui.adoc

@@ -10,7 +10,7 @@
 +
 *Default:* `False`
 
-|**UI_V2_REPO_SETTINGS** |Boolean | When set to `True`, enables repository settings in the {productname} v2 UI.
+|**FEATURE_UI_V2_REPO_SETTINGS** |Boolean | When set to `True`, enables repository settings in the {productname} v2 UI.
 +
 *Default:* `False` 
 |===

modules/config-preconfigure-automation.adoc

@@ -47,39 +47,17 @@ FEATURE_USER_CREATION: false
 ...
 ----
 
-[id="enabling-new-functionality-38"]
-== Enabling new functionality in {productname} 3.8
+[id="enabling-new-functionality-310"]
+== Enabling new functionality in {productname} 3.10
 
 To use new {productname} 3.8 functions, enable some or all of the following features:
 
 [source,yaml]
 ----
-...
 FEATURE_UI_V2: true
-FEATURE_LISTEN_IP_VERSION:
-FEATURE_SUPERUSERS_FULL_ACCESS: true
-GLOBAL_READONLY_SUPER_USERS:
-      -
-FEATURE_RESTRICTED_USERS: true
-RESTRICTED_USERS_WHITELIST:
-      -
-...
-----
-
-[id="enabling-new-functionality-37"]
-== Enabling new functionality in {productname} 3.7
-
-To use new {productname} 3.7 functions, enable some or all of the following features:
-
-[source,yaml]
-----
-...
-FEATURE_QUOTA_MANAGEMENT: true
-FEATURE_BUILD_SUPPORT: true
-FEATURE_PROXY_CACHE: true
-FEATURE_STORAGE_REPLICATION: true
-DEFAULT_SYSTEM_REJECT_QUOTA_BYTES: 102400000
-...
+FEATURE_UI_V2_REPO_SETTINGS: true
+FEATURE_AUTO_PRUNE: true
+ROBOTS_DISALLOW: false
 ----
 
 [id="suggested-configuration-for-automation"]

modules/config-updates-310.adoc

@@ -24,7 +24,7 @@ With {productname} 3.10, deployments can be configured to automatically prune ol
  +
 *Default*: `False`
 
-|**UI_V2_REPO_SETTINGS** |Boolean | When set to `True`, enables repository settings in the {productname} v2 UI.
+|**FEATURE_UI_V2_REPO_SETTINGS** |Boolean | When set to `True`, enables repository settings in the {productname} v2 UI.
  +
 *Default:* `False` 
 |===

modules/rn_3_10_0.adoc

@@ -17,7 +17,7 @@ For more information, see the link:https://access.redhat.com/support/policy/upda
 
 The following updates have been made to {productname}.
 
-[id="3-10-namespace-auto-pruning"]
+[id="namespace-auto-pruning-310-rn"]
 === Namespace auto-pruning
 
 With {productname} 3.10, {productname} administrators can set up auto-pruning policies on namespaces (both users and organization). This feature allows for image tags to be automatically deleted within a namespace based on specified criteria. For this release, two policies have been added:
@@ -36,7 +36,7 @@ In {productname} 3.8, a new UI was introduced as a technology preview feature. W
 
 * With this update, a *Settings* page has been added for {productname} organizations. {productname} administrators can edit their preferences, billing information, and set organization types from this page.
 
-* With this update, a *Settings* page has been added for {productname} repositories. This page must be enabled by setting `UI_V2_REPO_SETTINGS` to `true` in your `config.yaml` file. This page allows users to create and set robot permissions, create events and notifications, set repository visibility, and delete repositories.
+* With this update, a *Settings* page has been added for {productname} repositories. This page must be enabled by setting `FEATURE_UI_V2_REPO_SETTINGS` to `true` in your `config.yaml` file. This page allows users to create and set robot permissions, create events and notifications, set repository visibility, and delete repositories.
 
 * With this update, bulk managing robot account repository access is available on the {productname} v2 UI. Users can now easily add a robot account to multiple repositories using the v2 UI. 
 
@@ -113,7 +113,7 @@ The following configuration fields have been added for the auto-pruning feature:
 [id="v2-ui-repo-settings-config-field"]
 == {productname} v2 UI repository settings configuration field
 
-* **UI_V2_REPO_SETTINGS**: When set to `True`, enables repository settings in the {productname} v2 UI.
+* **FEATURE_UI_V2_REPO_SETTINGS**: When set to `True`, enables repository settings in the {productname} v2 UI.
 +
 *Default:* `False`
 
@@ -122,7 +122,7 @@ The following configuration fields have been added for the auto-pruning feature:
 
 The following updates have been made to the {productname} Operator:
 
-* The config editor has been removed from the {productname} Operator on {ocp} deployments. 
+* The config editor has been removed from the {productname} Operator on {ocp} deployments. As a result, the `quay-config-editor` pod no longer deploys, and users cannot check the status of the config editor route. Additionally, the Config Editor Endpoint no longer generates on the {productname} Operator *Details* page. 
 +
 By default, the config editor was deployed for every `QuayRegistry` instance, which made it difficult to establish an audit trail over the registry's configuration. Anyone with access to the namespace, config editor secret, and config editor route could use the editor to make changes to {productname}'s configuration, and their identity was no logged in the system. Removing the config editor forces all changes through the config bundle property of the `QuayRegistry` resource, which points to a secret, which is then subject to native Kubernetes auditing and logging. 
 
@@ -198,10 +198,11 @@ Some features available in previous releases have been deprecated or removed. De
 |General Availability
 |-
 |-
+
 |link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/manage_red_hat_quay/index?lb_target=stage#red-hat-quay-namespace-auto-pruning-overview[{productname} namespace auto-pruning overview]
 |General Availability
-|
-|
+|-
+|-
 
 |link:https://access.redhat.com/documentation/en-us/red_hat_quay/3.9/html-single/manage_red_hat_quay/index#operator-georepl-site-removal[Single site geo-replication removal]
 |General Availability

modules/upgrading-geo-repl-quay-operator.adoc

@@ -68,7 +68,6 @@ oc get pods -n <quay-namespace>
 quay-operator.v3.7.1-6f9d859bd-p5ftc               1/1     Running     0             12m
 quayregistry-clair-postgres-7487f5bd86-xnxpr       1/1     Running     1 (12m ago)   12m
 quayregistry-quay-app-upgrade-xq2v6                0/1     Completed   0             12m
-quayregistry-quay-config-editor-6dfdcfc44f-hlvwm   1/1     Running     0             73s
 quayregistry-quay-redis-84f888776f-hhgms           1/1     Running     0             12m
 ----