Final builders update (quay#1126)

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

Author: stevsmit

modules/build-enhancements.adoc

@@ -2,6 +2,14 @@
 [id="red-hat-quay-builders-enhancement"]
 = Virtual builds with {productname-ocp}
 
+ifeval::["{context}" == "use-quay"]
+The _builds_ feature has been moved to link:docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/builders_and_image_automation/index[Builders and image automation]. This chapter will be removed in a future version of {productname}.
+endif::[]
+
+ifeval::["{context}" == "quay-builders-image-automation"]
+The procedures in this section explain how to create an environment for _bare metal builds_ for {productname-ocp}.
+
+
 _Virtual builds_ can be run on virtualized machines with {productname-ocp}. With this method, the _build manager_ first creates the `Job Object` resource. Then, the `Job Object` creates a pod using the `quay-builder-image`. The `quay-builder-image` contains the `quay-builder` binary and the Podman service. The created pod runs as `unprivileged`. The `quay-builder` binary then builds the image while communicating status and retrieving build information from the _build manager_.
 
 [id="quay-builds-limitations"]
@@ -11,4 +19,5 @@ The following limitations apply to the _virtual builds_ feature:
 
 * Running _virtual builds_ with {productname-ocp} in an unprivileged context might cause some commands that were working under the previous build strategy to fail. Attempts to change the build strategy could potentially cause performance issues and reliability with the build.
 
-* Running _virtual builds_ directly in a container does not have the same isolation as using virtual machines. Changing the build environment might also cause builds that were previously working to fail. 
+* Running _virtual builds_ directly in a container does not have the same isolation as using virtual machines. Changing the build environment might also cause builds that were previously working to fail.
+endif::[]

modules/proc_use-quay-build-workers-dockerfiles.adoc

@@ -3,7 +3,7 @@
 = Bare metal builds with {productname-ocp}
 
 ifeval::["{context}" == "use-quay"]
-The _builds_ feature has been moved to link:docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/builders_and_image_automation/index[Builders and image automation]. This section will be removed in a future version of {productname}.
+The _builds_ feature has been moved to link:docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/builders_and_image_automation/index[Builders and image automation]. This chapter will be removed in a future version of {productname}.
 endif::[]
 
 ifeval::["{context}" == "quay-builders-image-automation"]

use_quay/master.adoc

@@ -139,9 +139,9 @@ include::modules/proxy-cache-leveraging-storage-quota-limits.adoc[leveloffset=+2
 
 // Virtual builders
 include::modules/build-enhancements.adoc[leveloffset=+1]
-include::modules/build-enhanced-arch.adoc[leveloffset=+2]
-include::modules/build-limitations.adoc[leveloffset=+2]
-include::modules/builders-virtual-environment.adoc[leveloffset=+2]
+//include::modules/build-enhanced-arch.adoc[leveloffset=+2]
+//include::modules/build-limitations.adoc[leveloffset=+2]
+//include::modules/builders-virtual-environment.adoc[leveloffset=+2]
 
 //api
 include::modules/proc_use-api.adoc[leveloffset=+1]