Merge pull request #52711 from michaelryanpeter/OSDOCS-4533-CIT-Remove-xrefs-in-osdk-common-prereq.adoc

OSDOCS-4533: CIT Remove xrefs in module and clean up

Author: michaelryanpeter

modules/osdk-common-prereqs.adoc

@@ -33,24 +33,24 @@ endif::[]
 [id="osdk-common-prereqs_{context}"]
 = Prerequisites
 
-- xref:../../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[Operator SDK CLI installed]
-- xref:../../../cli_reference/openshift_cli/getting-started-cli.adoc#getting-started-cli[OpenShift CLI (`oc`) v{product-version}+ installed]
+* Operator SDK CLI installed
+* OpenShift CLI (`oc`) v{product-version}+ installed
 ifdef::golang[]
-- link:https://golang.org/dl/[Go] v1.18+
+* link:https://golang.org/dl/[Go] v1.18+
 endif::[]
 ifdef::ansible[]
-- link:https://docs.ansible.com/ansible/2.9/index.html[Ansible] v2.9.0
-- link:https://ansible-runner.readthedocs.io/en/latest/install.html[Ansible Runner] v2.0.2+
-- link:https://github.com/ansible/ansible-runner-http[Ansible Runner HTTP Event Emitter plug-in] v1.0.0+
-- link:https://www.python.org/downloads/[Python] 3.8.6+
-- link:https://pypi.org/project/openshift/[OpenShift Python client] v0.12.0+
+* link:https://docs.ansible.com/ansible/2.9/index.html[Ansible] v2.9.0
+* link:https://ansible-runner.readthedocs.io/en/latest/install.html[Ansible Runner] v2.0.2+
+* link:https://github.com/ansible/ansible-runner-http[Ansible Runner HTTP Event Emitter plug-in] v1.0.0+
+* link:https://www.python.org/downloads/[Python] 3.8.6+
+* link:https://pypi.org/project/openshift/[OpenShift Python client] v0.12.0+
 endif::[]
 ifdef::java[]
-- link:https://java.com/en/download/help/download_options.html[Java] v11+
-- link:https://maven.apache.org/install.html[Maven] v3.6.3+
+* link:https://java.com/en/download/help/download_options.html[Java] v11+
+* link:https://maven.apache.org/install.html[Maven] v3.6.3+
 endif::[]
-- Logged into an {product-title} {product-version} cluster with `oc` with an account that has `cluster-admin` permissions
-- To allow the cluster to pull the image, the repository where you push your image must be set as public, or you must configure an image pull secret
+* Logged into an {product-title} {product-version} cluster with `oc` with an account that has `cluster-admin` permissions
+* To allow the cluster to pull the image, the repository where you push your image must be set as public, or you must configure an image pull secret
 
 ifeval::["{context}" == "osdk-ansible-quickstart"]
 :!ansible:

operators/operator_sdk/ansible/osdk-ansible-quickstart.adoc

@@ -11,6 +11,12 @@ The Operator SDK includes options for generating an Operator project that levera
 To demonstrate the basics of setting up and running an link:https://docs.ansible.com/ansible/latest/index.html[Ansible]-based Operator using tools and libraries provided by the Operator SDK, Operator developers can build an example Ansible-based Operator for Memcached, a distributed key-value store, and deploy it to a cluster.
 
 include::modules/osdk-common-prereqs.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[Installing the Operator SDK CLI]
+* xref:../../../cli_reference/openshift_cli/getting-started-cli.adoc#getting-started-cli[Getting started with the OpenShift CLI]
+
 include::modules/osdk-quickstart.adoc[leveloffset=+1]
 
 [id="osdk-ansible-quickstart-next-steps"]

operators/operator_sdk/ansible/osdk-ansible-tutorial.adoc

@@ -25,6 +25,11 @@ This tutorial goes into greater detail than xref:../../../operators/operator_sdk
 
 include::modules/osdk-common-prereqs.adoc[leveloffset=+1]
 
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[Installing the Operator SDK CLI]
+* xref:../../../cli_reference/openshift_cli/getting-started-cli.adoc#getting-started-cli[Getting started with the OpenShift CLI]
+
 include::modules/osdk-create-project.adoc[leveloffset=+1]
 include::modules/osdk-project-file.adoc[leveloffset=+2]
 
@@ -48,5 +53,5 @@ include::modules/osdk-create-cr.adoc[leveloffset=+1]
 [id="osdk-ansible-tutorial-addtl-resources"]
 == Additional resources
 
-- See xref:../../../operators/operator_sdk/ansible/osdk-ansible-project-layout.adoc#osdk-ansible-project-layout[Project layout for Ansible-based Operators] to learn about the directory structures created by the Operator SDK.
-- If a xref:../../../networking/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[cluster-wide egress proxy is configured], cluster administrators can xref:../../../operators/admin/olm-configuring-proxy-support.adoc#olm-configuring-proxy-support[override the proxy settings or inject a custom CA certificate] for specific Operators running on Operator Lifecycle Manager (OLM).
+* See xref:../../../operators/operator_sdk/ansible/osdk-ansible-project-layout.adoc#osdk-ansible-project-layout[Project layout for Ansible-based Operators] to learn about the directory structures created by the Operator SDK.
+* If a xref:../../../networking/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[cluster-wide egress proxy is configured], cluster administrators can xref:../../../operators/admin/olm-configuring-proxy-support.adoc#olm-configuring-proxy-support[override the proxy settings or inject a custom CA certificate] for specific Operators running on Operator Lifecycle Manager (OLM).

operators/operator_sdk/golang/osdk-golang-quickstart.adoc

@@ -9,6 +9,12 @@ toc::[]
 To demonstrate the basics of setting up and running a Go-based Operator using tools and libraries provided by the Operator SDK, Operator developers can build an example Go-based Operator for Memcached, a distributed key-value store, and deploy it to a cluster.
 
 include::modules/osdk-common-prereqs.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[Installing the Operator SDK CLI]
+* xref:../../../cli_reference/openshift_cli/getting-started-cli.adoc#getting-started-cli[Getting started with the OpenShift CLI]
+
 include::modules/osdk-quickstart.adoc[leveloffset=+1]
 
 [id="osdk-golang-quickstart-next-steps"]

operators/operator_sdk/golang/osdk-golang-tutorial.adoc

@@ -21,6 +21,11 @@ This tutorial goes into greater detail than xref:../../../operators/operator_sdk
 
 include::modules/osdk-common-prereqs.adoc[leveloffset=+1]
 
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[Installing the Operator SDK CLI]
+* xref:../../../cli_reference/openshift_cli/getting-started-cli.adoc#getting-started-cli[Getting started with the OpenShift CLI]
+
 include::modules/osdk-create-project.adoc[leveloffset=+1]
 include::modules/osdk-project-file.adoc[leveloffset=+2]
 include::modules/osdk-golang-manager.adoc[leveloffset=+2]
@@ -57,5 +62,5 @@ include::modules/osdk-create-cr.adoc[leveloffset=+1]
 [role="_additional-resources"]
 == Additional resources
 
-- See xref:../../../operators/operator_sdk/golang/osdk-golang-project-layout.adoc#osdk-golang-project-layout[Project layout for Go-based Operators] to learn about the directory structures created by the Operator SDK.
-- If a xref:../../../networking/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[cluster-wide egress proxy is configured], cluster administrators can xref:../../../operators/admin/olm-configuring-proxy-support.adoc#olm-configuring-proxy-support[override the proxy settings or inject a custom CA certificate] for specific Operators running on Operator Lifecycle Manager (OLM).
+* See xref:../../../operators/operator_sdk/golang/osdk-golang-project-layout.adoc#osdk-golang-project-layout[Project layout for Go-based Operators] to learn about the directory structures created by the Operator SDK.
+* If a xref:../../../networking/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[cluster-wide egress proxy is configured], cluster administrators can xref:../../../operators/admin/olm-configuring-proxy-support.adoc#olm-configuring-proxy-support[override the proxy settings or inject a custom CA certificate] for specific Operators running on Operator Lifecycle Manager (OLM).

operators/operator_sdk/helm/osdk-helm-quickstart.adoc

@@ -11,6 +11,12 @@ The Operator SDK includes options for generating an Operator project that levera
 To demonstrate the basics of setting up and running an link:https://helm.sh/docs/[Helm]-based Operator using tools and libraries provided by the Operator SDK, Operator developers can build an example Helm-based Operator for Nginx and deploy it to a cluster.
 
 include::modules/osdk-common-prereqs.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[Installing the Operator SDK CLI]
+* xref:../../../cli_reference/openshift_cli/getting-started-cli.adoc#getting-started-cli[Getting started with the OpenShift CLI]
+
 include::modules/osdk-quickstart.adoc[leveloffset=+1]
 
 [id="osdk-helm-quickstart-next-steps"]

operators/operator_sdk/helm/osdk-helm-tutorial.adoc

@@ -25,6 +25,11 @@ This tutorial goes into greater detail than xref:../../../operators/operator_sdk
 
 include::modules/osdk-common-prereqs.adoc[leveloffset=+1]
 
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[Installing the Operator SDK CLI]
+* xref:../../../cli_reference/openshift_cli/getting-started-cli.adoc#getting-started-cli[Getting started with the OpenShift CLI]
+
 include::modules/osdk-create-project.adoc[leveloffset=+1]
 include::modules/osdk-helm-existing-chart.adoc[leveloffset=+2]
 include::modules/osdk-project-file.adoc[leveloffset=+2]
@@ -50,5 +55,5 @@ include::modules/osdk-create-cr.adoc[leveloffset=+1]
 [role="_additional-resources"]
 == Additional resources
 
-- See xref:../../../operators/operator_sdk/helm/osdk-helm-project-layout.adoc#osdk-helm-project-layout[Project layout for Helm-based Operators] to learn about the directory structures created by the Operator SDK.
-- If a xref:../../../networking/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[cluster-wide egress proxy is configured], cluster administrators can xref:../../../operators/admin/olm-configuring-proxy-support.adoc#olm-configuring-proxy-support[override the proxy settings or inject a custom CA certificate] for specific Operators running on Operator Lifecycle Manager (OLM).
+* See xref:../../../operators/operator_sdk/helm/osdk-helm-project-layout.adoc#osdk-helm-project-layout[Project layout for Helm-based Operators] to learn about the directory structures created by the Operator SDK.
+* If a xref:../../../networking/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[cluster-wide egress proxy is configured], cluster administrators can xref:../../../operators/admin/olm-configuring-proxy-support.adoc#olm-configuring-proxy-support[override the proxy settings or inject a custom CA certificate] for specific Operators running on Operator Lifecycle Manager (OLM).

operators/operator_sdk/helm/osdk-hybrid-helm.adoc

@@ -18,12 +18,17 @@ include::snippets/technology-preview.adoc[]
 
 This tutorial walks through the following process using the Hybrid Helm Operator:
 
-- Create a `Memcached` deployment through a Helm chart if it does not exist
-- Ensure that the deployment size is the same as specified by `Memcached` custom resource (CR) spec
-- Create a `MemcachedBackup` deployment by using the Go API
+* Create a `Memcached` deployment through a Helm chart if it does not exist
+* Ensure that the deployment size is the same as specified by `Memcached` custom resource (CR) spec
+* Create a `MemcachedBackup` deployment by using the Go API
 
 include::modules/osdk-common-prereqs.adoc[leveloffset=+1]
 
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[Installing the Operator SDK CLI]
+* xref:../../../cli_reference/openshift_cli/getting-started-cli.adoc#getting-started-cli[Getting started with the OpenShift CLI]
+
 include::modules/osdk-hh-create-project.adoc[leveloffset=+1]
 .Additional resources
 

operators/operator_sdk/java/osdk-java-quickstart.adoc

@@ -11,6 +11,12 @@ toc::[]
 To demonstrate the basics of setting up and running a Java-based Operator using tools and libraries provided by the Operator SDK, Operator developers can build an example Java-based Operator for Memcached, a distributed key-value store, and deploy it to a cluster.
 
 include::modules/osdk-common-prereqs.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[Installing the Operator SDK CLI]
+* xref:../../../cli_reference/openshift_cli/getting-started-cli.adoc#getting-started-cli[Getting started with the OpenShift CLI]
+
 include::modules/osdk-quickstart.adoc[leveloffset=+1]
 
 [id="next-steps_osdk-java-quickstart"]

operators/operator_sdk/java/osdk-java-tutorial.adoc

@@ -23,6 +23,11 @@ This tutorial goes into greater detail than xref:../../../operators/operator_sdk
 
 include::modules/osdk-common-prereqs.adoc[leveloffset=+1]
 
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[Installing the Operator SDK CLI]
+* xref:../../../cli_reference/openshift_cli/getting-started-cli.adoc#getting-started-cli[Getting started with the OpenShift CLI]
+
 include::modules/osdk-create-project.adoc[leveloffset=+1]
 include::modules/osdk-project-file.adoc[leveloffset=+2]
 
@@ -53,5 +58,5 @@ include::modules/osdk-deploy-olm.adoc[leveloffset=+3]
 [id="additional-resources_osdk-java-tutorial"]
 == Additional resources
 
-- See xref:../../../operators/operator_sdk/java/osdk-java-project-layout.adoc#osdk-java-project-layout[Project layout for Java-based Operators] to learn about the directory structures created by the Operator SDK.
-- If a xref:../../../networking/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[cluster-wide egress proxy is configured], cluster administrators can xref:../../../operators/admin/olm-configuring-proxy-support.adoc#olm-configuring-proxy-support[override the proxy settings or inject a custom CA certificate] for specific Operators running on Operator Lifecycle Manager (OLM).
+* See xref:../../../operators/operator_sdk/java/osdk-java-project-layout.adoc#osdk-java-project-layout[Project layout for Java-based Operators] to learn about the directory structures created by the Operator SDK.
+* If a xref:../../../networking/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[cluster-wide egress proxy is configured], cluster administrators can xref:../../../operators/admin/olm-configuring-proxy-support.adoc#olm-configuring-proxy-support[override the proxy settings or inject a custom CA certificate] for specific Operators running on Operator Lifecycle Manager (OLM).