Further refactor

- Move the the OLM tagging module to the Next steps section
  * The language in this module is not consistent with the rest of the
  content. I need to rework this after 4.14 GA
- Move the validation module to the run bundle validate docs
- Include the bundle and deploy steps in the Next steps section
  Otherwise, your changes won't sync

modules/osdk-multi-arch-validate.adoc

@@ -4,7 +4,7 @@
 
 :_content-type: PROCEDURE
 [id="osdk-multi-arch-validate_{context}"]
-= Validating your Operator's support for multiple architectures
+= Validating your Operator's multi-platform readiness
 
 You can use the Operator SDK `bundle validate` command to verify that the images defined in the cluster service version (CSV) deployment spec comply with the best practices as defined by the Operator Framework community.
 

operators/operator_sdk/osdk-bundle-validate.adoc

@@ -17,3 +17,9 @@ include::modules/osdk-bundle-validate-tests.adoc[leveloffset=+1]
 * xref:../../operators/understanding/olm-packaging-format.adoc#olm-bundle-format_olm-packaging-format[Bundle format]
 
 include::modules/osdk-bundle-validate-run.adoc[leveloffset=+1]
+include::modules/osdk-multi-arch-validate.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../operators/operator_sdk/osdk-multi-arch-support.adoc#osdk-multi-platform-support[Configuring Operator projects for multi-platform support]

operators/operator_sdk/osdk-multi-arch-support.adoc

@@ -1,6 +1,6 @@
 :_content-type: ASSEMBLY
-[id="osdk-multiple-platform-support"]
-= Configuring Operator projects to support multiple architectures and operating systems
+[id="osdk-multi-platform-support"]
+= Configuring Operator projects for multi-platform support
 include::_attributes/common-attributes.adoc[]
 :context: osdk-multi-arch
 
@@ -27,17 +27,21 @@ include::modules/osdk-multi-arch-node-reqs.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
 * xref:../../nodes/scheduling/nodes-scheduler-node-affinity.adoc#nodes-scheduler-node-affinity-configuring-required_nodes-scheduler-node-affinity[Configuring a required node affinity rule]
+* xref:../../nodes/scheduling/nodes-scheduler-node-affinity.adoc#nodes-scheduler-node-affinity-example_nodes-scheduler-node-affinity[Sample node affinity rules]
 
 include::modules/osdk-multi-arch-node-preference.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
 * xref:../../nodes/scheduling/nodes-scheduler-node-affinity.adoc#nodes-scheduler-node-affinity-configuring-preferred_nodes-scheduler-node-affinity[Configuring a preferred node affinity rule]
 
-include::modules/osdk-multi-arch-validate.adoc[leveloffset=+1]
-
-[role="_additional-resources"]
-[id="additional-resources_osdk-multi-arch-support.adoc"]
-== Additional resources
+[role="_next-steps"]
+[id="next-steps_osdk-multi-arch-support.adoc"]
+== Next steps
 
-* xref:../../nodes/scheduling/nodes-scheduler-node-affinity.adoc#nodes-scheduler-node-affinity-example_nodes-scheduler-node-affinity[Sample node affinity rules]
+* xref:../../operators/operator_sdk/osdk-generating-csvs.adoc#olm-enabling-operator-for-multi-arch_osdk-generating-csvs[Label the platforms your Operator supports for Operator Lifecycle Manager (OLM)]
+* Bundle your Operator and Deploy with OLM
+** xref:../../operators/operator_sdk/golang/osdk-golang-tutorial.adoc#osdk-bundle-deploy-olm_osdk-golang-tutorial[Go-based Operator projects]
+** xref:../../operators/operator_sdk/ansible/osdk-ansible-tutorial.adoc#osdk-bundle-deploy-olm_osdk-ansible-tutorial[Ansible-based Operator projects]
+** xref:../../operators/operator_sdk/helm/osdk-helm-tutorial.html#osdk-bundle-deploy-olm_osdk-helm-tutorial[Helm-bsed Operator projects]
+* xref:../../operators/operator_sdk/osdk-bundle-validate.html#osdk-multi-arch-validate_osdk-bundle-validate[Validate your Operator's multi-platform readiness]