Merge pull request #20261 from adellape/understanding_operatorhub

Add info on packaging to Understanding the OperatorHub

Author: adellape

modules/olm-operatorhub-overview.adoc

@@ -36,3 +36,15 @@ GitHub repository. No official support.
 If you have not added any Custom Operators, the Custom category does not appear in
 the web console on your OperatorHub.
 |===
+
+Operators on the OperatorHub are packaged to run on OLM. This includes a YAML
+file called a ClusterServiceVersion (CSV) containing all of the CRDs, RBAC
+rules, Deployments, and container images required to install and securely run the
+Operator. It also contains user-visible information like a description of its
+features and supported Kubernetes versions.
+
+The Operator SDK can be used to assist developers packaging their Operators for
+use on OLM and the OperatorHub. If you have a commercial application that you
+want to make accessible to your customers, get it included using the
+certification workflow provided by Red Hat's ISV partner portal at
+link:https://connect.redhat.com[connect.redhat.com].

operators/olm-understanding-operatorhub.adoc

@@ -8,4 +8,11 @@ toc::[]
 This guide outlines the architecture of the OperatorHub.
 
 include::modules/olm-operatorhub-overview.adoc[leveloffset=+1]
+.Additional resources
+
+* xref:../operators/operator_sdk/osdk-getting-started.adoc#osdk-getting-started[Getting started with the Operator SDK]
+* xref:../operators/operator_sdk/osdk-generating-csvs.adoc#osdk-generating-csvs[Generating a ClusterServiceVersion (CSV)]
+* xref:../operators/understanding_olm/olm-understanding-olm.adoc#olm-upgrades_olm-understanding-olm[Operator installation and upgrade workflow in OLM]
+* link:https://connect.redhat.com[Red Hat Partner Connect]
+
 include::modules/olm-operatorhub-architecture.adoc[leveloffset=+1]