Merge pull request #82372 from michaelryanpeter/OSDOCS-11121-remove-rukpak

OSDOCS#11121: [OLMv1] Remove references to RukPak and bundle deployments

Author: michaelryanpeter

modules/olm-installing-po-after.adoc renamed to _unused_topics/olm-installing-po-after.adoc

@@ -14,4 +14,3 @@ Currently, the _registry provisioner_ is implemented and included with RukPak. A
 A provisioner is assigned a unique ID and is responsible for reconciling bundles and `BundleDeployment` objects with a `spec.provisionerClassName` field that matches that particular ID. For example, the registry provisioner is able to unpack a given `registry+v1` bundle onto a cluster and then instantiate it, making the content of the bundle available in the cluster.
 
 A provisioner places a watch on `BundleDeployment` resources that refer to the provisioner explicitly. For a given bundle, the provisioner unpacks the contents of the bundle onto the cluster. Then, given a `BundleDeployment` resource referring to that bundle, the provisioner installs the bundle contents and is responsible for managing the lifecycle of those resources.
-

modules/olm-rukpak-about.adoc renamed to _unused_topics/olm-rukpak-about.adoc

@@ -43,7 +43,10 @@ $ curl -L http://localhost:8080/catalogs/redhat-operators/all.json \
 
 . Run one of the following commands to return a list of Operators and extensions in a catalog.
 +
-include:snippets/olmv1-tp-extension-support.adoc[]
+[IMPORTANT]
+====
+include::snippets/olmv1-tp-extension-support.adoc[]
+====
 +
 * Get a list of all the Operators and extensions from the local catalog file by running the following command:
 +

modules/olm-rukpak-bd.adoc renamed to _unused_topics/olm-rukpak-bd.adoc

@@ -240,65 +240,3 @@ The value of `False` in the `status` field indicates that the `reason: Deprecate
 `resolvedBundle.name`:: Displays the name of the resolved bundle.
 `resolvedBundle.version`:: Displays the version of the resolved bundle.
 ====
-
-. Get information about your bundle deployment by running the following command:
-+
-[source,terminal]
-----
-$ oc get bundleDeployment pipelines-operator -o yaml
-----
-+
-.Example output
-[%collapsible]
-====
-[source,text]
-----
-apiVersion: core.rukpak.io/v1alpha2
-kind: BundleDeployment
-metadata:
-  creationTimestamp: "2024-06-10T17:50:58Z"
-  finalizers:
-  - core.rukpak.io/delete-cached-bundle
-  generation: 1
-  name: pipelines-operator
-  ownerReferences:
-  - apiVersion: olm.operatorframework.io/v1alpha1
-    blockOwnerDeletion: true
-    controller: true
-    kind: ClusterExtension
-    name: pipelines-operator
-    uid: c54237be-cde4-46d4-9b31-d0ec6acc19bf
-  resourceVersion: "53414"
-  uid: 74367cfc-578e-4da0-815f-fe40f3ca5d1c
-spec:
-  installNamespace: openshift-operators
-  provisionerClassName: core-rukpak-io-registry
-  source:
-    image:
-      ref: registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:dd3d18367da2be42539e5dde8e484dac3df33ba3ce1d5bcf896838954f3864ec
-    type: image
-status:
-  conditions:
-  - lastTransitionTime: "2024-06-10T17:51:09Z"
-    message: Successfully unpacked the image Bundle
-    reason: UnpackSuccessful
-    status: "True"
-    type: Unpacked
-  - lastTransitionTime: "2024-06-10T17:51:10Z"
-    message: Instantiated bundle pipelines-operator successfully
-    reason: InstallationSucceeded
-    status: "True"
-    type: Installed
-  - lastTransitionTime: "2024-06-10T17:51:19Z"
-    message: BundleDeployment is healthy
-    reason: Healthy
-    status: "True"
-    type: Healthy
-  contentURL: https://core.openshift-rukpak.svc/bundles/pipelines-operator.tgz
-  observedGeneration: 1
-  resolvedSource:
-    image:
-      ref: registry.redhat.io/openshift-pipelines/pipelines-operator-bundle@sha256:dd3d18367da2be42539e5dde8e484dac3df33ba3ce1d5bcf896838954f3864ec
-    type: image
-----
-====

modules/olm-rukpak-provisioner.adoc renamed to _unused_topics/olm-rukpak-provisioner.adoc

@@ -72,16 +72,3 @@ For instructions about creating file-based catalogs by using the `opm` CLI, see
 For reference documentation about the `opm` CLI commands related to managing file-based catalogs, see xref:../../cli_reference/opm/cli-opm-ref.adoc#cli-opm-ref[CLI tools].
 
 include::modules/olm-fb-catalogs-automation.adoc[leveloffset=+2]
-
-// Tech Preview features should not be included in ROSA/OSD.
-ifndef::openshift-dedicated,openshift-rosa[]
-include::modules/olm-rukpak-about.adoc[leveloffset=+1]
-[role="_additional-resources"]
-.Additional resources
-
-* xref:../../operators/olm_v1/index.adoc#olmv1-about[About {olmv1} (Technology Preview)]
-* xref:../../operators/understanding/olm-packaging-format.adoc#olm-bundle-format_olm-packaging-format[{olmv0-caps} bundle format]
-
-include::modules/olm-rukpak-provisioner.adoc[leveloffset=+2]
-include::modules/olm-rukpak-bd.adoc[leveloffset=+2]
-endif::openshift-dedicated,openshift-rosa[]