Adds v2 UI default to RNs (quay#1476)

stevsmit · Steven Smith · web-flow · commit c1d6731b33cf · 2025-11-12T11:05:20.000-05:00
Co-authored-by: Steven Smith &lt;stevsmit@stevsmit-thinkpadt14gen4.remote.csb&gt;
diff --git a/manage_quay/master.adoc b/manage_quay/master.adoc
@@ -21,7 +21,7 @@ further configure and manage that deployment. Topics covered here include:
 * Setting up geo-replication
 * Troubleshooting {productname}
 
-For a complete list of {productname} configuration fields, see the link:https://access.redhat.com/documentation/en-us/red_hat_quay/3.8/html-single/configure_red_hat_quay/index[Configure {productname}] page.
+For a complete list of {productname} configuration fields, see the link:https://access.redhat.com/documentation/en-us/red_hat_quay/3.15/html-single/configure_red_hat_quay/index[Configure {productname}] page.
 
 include::modules/proc_manage-advanced-config.adoc[leveloffset=+1]
 
@@ -63,11 +63,8 @@ include::modules/understanding-action-logs.adoc[leveloffset=+2]
 
 :context: security-scanning
 
-include::modules/clair-vulnerability-scanner-overview.adoc[leveloffset=+1]
-include::modules/clair-vulnerability-scanner-hosts.adoc[leveloffset=+2]
-include::modules/clair-standalone-configure.adoc[leveloffset=+2]
-include::modules/clair-openshift.adoc[leveloffset=+2]
-include::modules/clair-testing.adoc[leveloffset=+2]
+include::modules/about-clair.adoc[leveloffset=+1]
+
 
 :context: manage_quay
 
@@ -163,8 +160,6 @@ include::modules/standalone-to-operator-backup-restore.adoc[leveloffset=+1]
 
 include::modules/garbage-collection.adoc[leveloffset=+1]
 
-include::modules/using-v2-ui.adoc[leveloffset=+1]
-
 include::modules/health-check-quay.adoc[leveloffset=+1]
 
 
diff --git a/modules/about-clair.adoc b/modules/about-clair.adoc
@@ -22,6 +22,11 @@ If Clair finds vulnerabilities from NVD, a detailed and standardized assessment
 * *Inform Remediation Strategies*. CVSS enrichment data can guide {quayio} users in developing appropriate remediation strategies. 
 * *Compliance and Reporting*. Integrating CVSS data into reports generated by Clair can help organizations demonstrate their commitment to addressing security vulnerabilities and complying with industry standards and regulations.
 
+ifeval::["{context}" == "security-scanning"]
+Documentation for installing and configuring Clair can be found in link:https://docs.redhat.com/en/documentation/red_hat_quay/3.15/html/vulnerability_reporting_with_clair_on_red_hat_quay/index[Vulnerability reporting with Clair on {productname}].
+endif::[]
+
+
 ifeval::["{context}" == "clair"]
 [id="clair-releases"]
 == Clair releases
@@ -95,6 +100,7 @@ Clair 4.7 was released as part of {productname} 3.9, and includes support for th
 * Clair now supports Java, Golang, Python, and Ruby dependencies. 
 endif::[]
 
+ifeval::["{context}" == "clair,quay-io"]
 [id="vuln-database-clair"]
 == Clair vulnerability databases
 
@@ -131,6 +137,7 @@ When an image that contains packages from a language unsupported by Clair is pus
 ====
 Scanned images are indexed, and a vulnerability report is created, but it might omit data from certain unsupported languages. For example, if your container image contains a Lua application, feedback from Clair is not provided because Clair does not detect it. It can detect other languages used in the container image, and shows detected CVEs for those languages. As a result, Clair images are _fully scanned_ based on what it supported by Clair. 
 ====
+endif::[]
 
 ifeval::["{context}" == "clair"]
 [id="clair-containers"]
diff --git a/modules/deprecations-316.adoc b/modules/deprecations-316.adoc
@@ -4,7 +4,16 @@
 
 This section lists features, configuration options, and APIs that are deprecated in {productname} 3.16. Deprecated functionality remains available for now but is planned for removal in a future release. You should migrate away from these features to ensure compatibility with upcoming versions.
 
+[id="v1-deprecation"]
+== v1 UI deprecation notice
+
+With this release, the {productname} v1 UI (_legacy_ UI or _angular_ UI) is deprecated.
+
+Deprecation serves as an official notice that the v1 UI will be removed in a future release. Customers should begin planning their transition to the v2 UI. The exact version in which the v1 UI will be completely removed has not yet been determined, but it will be after version 3.16.
+
+The new v2 _react_-based UI is now the default UI. We encourage customers to explore the updated interfaces and workflows in preparation for this transition.
+
 [id="cso-deprecation"]
-== {cso} deprecation
+== {cso} deprecation notice
 
 The {cso} has been deprecated and is planned for removal in a future release of {productname} and {ocp}. The official replacement product of the {cso} is Red{nbsp}Hat Advanced Cluster Security for Kubernetes.
diff --git a/modules/new-features-and-enhancements-316.adoc b/modules/new-features-and-enhancements-316.adoc
@@ -4,6 +4,11 @@
 
 The following updates have been made to {productname}.
 
+[id="default-ui-v2-react"]
+== {productname} default UI
+
+With this release, the v2, _react_-based UI is now the default UI. Procedures throughout this documentation have been updated to reflect these changes.
+
 [id="image-pull-activity-tracking"]
 == Image pull activity tracking
 
diff --git a/modules/new-quay-config-fields-316.adoc b/modules/new-quay-config-fields-316.adoc
@@ -46,7 +46,9 @@ For more information, see link:https://docs.redhat.com/en/documentation/red_hat_
 [id="disable-v1-ui"]
 == Disabling the {productname} legacy UI completely
 
-The {productname} v2 UI is now the default UI. Users can toggle between the v1/legacy UI and the v2 UI by clicking their username and the *Legacy UI / Current UI* toggle. However, the following configuration fields are available to completely disable the legacy UI, or to set it as the default UI.
+The {productname} v2 UI is now the default UI. Users can toggle between the v1/legacy UI and the v2 UI by clicking their username and the *Legacy UI / Current UI* toggle when `FEATURE_UI_V2: true` is set in their `config.yaml` file.
+
+The following configuration fields are available to completely disable the legacy UI, or to set it as the default UI. However, users and administrators should remain aware that the v1 _legacy_ UI is deprecated and planned for removal in a future version of {productname}.
 
 .UI fields
 [cols="3a,1a,2a",options="header"]
diff --git a/modules/operator-ipv6-dual-stack.adoc b/modules/operator-ipv6-dual-stack.adoc
@@ -18,7 +18,6 @@ Use the following procedure to enable IPv6 support on your {productname} deploym
 
 .Prerequisites 
 
-* You have updated {productname} to at least version 3.8.
 * Your host and container software platform (Docker, Podman) must be configured to support IPv6. 
 
 .Procedure 
diff --git a/modules/proc_manage-ipv6-dual-stack.adoc b/modules/proc_manage-ipv6-dual-stack.adoc
@@ -13,7 +13,6 @@ Use the following procedure to enable IPv6 support on your standalone {productna
 
 .Prerequisites 
 
-* You have updated {productname} to 3.8.
 * Your host and container software platform (Docker, Podman) must be configured to support IPv6. 
 
 .Procedure 
@@ -53,10 +52,8 @@ If your environment is configured to IPv4, but the `FEATURE_LISTEN_IP_VERSION` c
 
 Use the following procedure to enable dual-stack (IPv4 and IPv6) support on your standalone {productname} deployment. 
 
-
 .Prerequisites 
 
-* You have updated {productname} to 3.8.
 * Your host and container software platform (Docker, Podman) must be configured to support IPv6. 
 
 .Procedure
diff --git a/modules/quay-feature-tracker.adoc b/modules/quay-feature-tracker.adoc
@@ -14,6 +14,8 @@ Some features available in previous releases have been deprecated or removed. De
 |===
 |Feature | Quay 3.16 | Quay 3.15 | Quay 3.14
 
+|v1 UI |Deprecated |Deprecated | General Availability
+
 |link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/use_red_hat_quay/index#viewing-model-card-information[Viewing model card information by using the v2 UI].
 |General Availability
 |General Availability
