Remove mention of the Operator SDK product / project

Author: michaelryanpeter

_attributes/common-attributes.adoc

@@ -223,10 +223,6 @@ endif::[]
 // logical volume manager storage
 :lvms-first: Logical Volume Manager (LVM) Storage
 :lvms: LVM Storage
-//Operator SDK version
-:osdk_ver: 1.38.0
-//Operator SDK version that shipped with the previous OCP 4.x release
-:osdk_ver_n1: 1.36.1
 //Version-agnostic OLM
 :olm-first: Operator Lifecycle Manager (OLM)
 :olm: OLM
@@ -381,4 +377,4 @@ endif::openshift-origin[]
 :rhoai-diy: Red{nbsp}Hat OpenShift AI Self-Managed
 :rhoai-cloud: Red{nbsp}Hat OpenShift AI Cloud Service
 :ai-first: artificial intelligence (AI)
-//RHEL AI attribute listed with RHEL family
+//RHEL AI attribute listed with RHEL family

contributing_to_docs/term_glossary.adoc

@@ -512,8 +512,6 @@ Operator that packages an application.
 .Examples of correct usage
 ====
 Install the etcd Operator.
-
-Build an Operator using the Operator SDK.
 ====
 
 See link:doc_guidelines.adoc#api-object-formatting[API object formatting] for

getting_started/openshift-overview.adoc

@@ -76,9 +76,6 @@ describes an application that can be deployed using the Helm CLI.
 
 * **xref:../operators/understanding/olm-what-operators-are.adoc#olm-what-operators-are[Understand Operators]**: Operators are the preferred method for creating on-cluster applications for {product-title} {product-version}. Learn about the Operator Framework and how to deploy applications using installed Operators into your projects.
 
-* **xref:../operators/operator_sdk/osdk-about.adoc#osdk-about[Develop Operators]**: Operators are the preferred method for creating on-cluster applications for {product-title} {product-version}. Learn the workflow for building, testing, and deploying Operators. Then, create your own Operators based on xref:../operators/operator_sdk/ansible/osdk-ansible-support.adoc#osdk-ansible-support[Ansible] or
-xref:../operators/operator_sdk/helm/osdk-helm-support.adoc#osdk-helm-support[Helm], or configure xref:../operators/operator_sdk/osdk-monitoring-prometheus.adoc#osdk-monitoring-prometheus[built-in Prometheus monitoring] using the Operator SDK.
-
 * **xref:../rest_api/overview/index.adoc#api-index[REST API reference]**: Learn about {product-title} application programming interface endpoints.
 
 === For administrators

modules/arch-olm-operators.adoc

@@ -32,8 +32,6 @@ All Operators listed in the Operator Hub marketplace should be available for ins
 ====
 endif::openshift-dedicated,openshift-rosa[]
 
-Developers can use the Operator SDK to help author custom Operators that take advantage of OLM features, as well. Their Operator can then be bundled and added to a custom catalog source, which can be added to a cluster and made available to users.
-
 [NOTE]
 ====
 OLM does not manage the cluster Operators that comprise the {product-title} architecture.

modules/olm-operator-framework.adoc

@@ -7,9 +7,6 @@
 
 The Operator Framework is a family of tools and capabilities to deliver on the customer experience described above. It is not just about writing code; testing, delivering, and updating Operators is just as important. The Operator Framework components consist of open source tools to tackle these problems:
 
-Operator SDK::
-The Operator SDK assists Operator authors in bootstrapping, building, testing, and packaging their own Operator based on their expertise without requiring knowledge of Kubernetes API complexities.
-
 Operator Lifecycle Manager::
 Operator Lifecycle Manager (OLM) controls the installation, upgrade, and role-based access control (RBAC) of Operators in a cluster. It is deployed by default in {product-title} {product-version}.
 

modules/olm-operator-maturity-model.adoc

@@ -11,6 +11,3 @@ One can however generalize the scale of the maturity of the encapsulated operati
 
 .Operator maturity model
 image::operator-maturity-model.png[]
-
-The above model also shows how these capabilities can best be developed through
-the Helm, Go, and Ansible capabilities of the Operator SDK.

modules/olm-operatorhub-overview.adoc

@@ -33,5 +33,3 @@ Cluster administrators can choose from catalogs grouped into the following categ
 endif::[]
 
 Operators on OperatorHub are packaged to run on OLM. This includes a YAML file called a cluster service version (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 OperatorHub. If you have a commercial application that you want to make accessible to your customers, get it included using the certification workflow provided on the Red Hat Partner Connect portal at link:https://connect.redhat.com[connect.redhat.com].

operators/understanding/olm-common-terms.adoc

@@ -6,6 +6,6 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-This topic provides a glossary of common terms related to the Operator Framework, including Operator Lifecycle Manager (OLM) and the Operator SDK.
+This topic provides a glossary of common terms related to the Operator Framework, including Operator Lifecycle Manager (OLM).
 
 include::snippets/of-terms-snippet.adoc[leveloffset=+0]