Merge pull request #368 from ritz303/ritz303-dbaas-1266

[DBAAS-1266] Removed the manual operator installation using OLM
RHEcosystemAppEng · Apr 12, 2023 · 3245892 · 3245892
2 parents da06d34 + 9ffc053
commit 3245892
Showing 1 changed file with 0 additions and 93 deletions.
diff --git a/docs/quick-start-guide/main.adoc b/docs/quick-start-guide/main.adoc
@@ -296,96 +296,3 @@ IMPORTANT: Database instances using a custom Oracle or custom SQL Server engine
 
 . Copy the **AWS Access key ID**, and the **AWS Secret access key**.
 // End
-
-// Appendix D : Manual installation using Operator Lifecycle Manager (OLM)
-[appendix]
-[id="installing-openshift-database-access-using-the-operator-lifecycle-manager"]
-
-== Installing OpenShift Database Access using the Operator Lifecycle Manager
-
-For some OpenShift cluster types, you must install the OpenShift Database Access operator by using the Operator Lifecycle Manager (OLM).
-
-.Prerequisites
-
-* OpenShift Container Platform 4.10 or higher.
-* A running OpenShift Dedicated or ARO cluster.
-
-.Procedure
-
-. Log into OpenShift by using the a command-line interface:
-+
-.Syntax
-[source,subs="verbatim,quotes"]
-----
-oc login --token=_TOKEN_ --server=_SERVER_URL_AND_PORT_
-----
-+
-.Example
-----
-$ oc login --token=sha256~ZvFDBvoIYAbVECixS4-WmkN4RfnNd8Neh3y1WuiFPXC --server=https://example.com:6443
-----
-+
-[NOTE]
-====
-You can find your command-line login token and URL from the OpenShift console.
-Log in to the OpenShift console.
-Click your user name, and click **Copy login command**.
-Offer your user name and password again, and click **Display Token** to view the command.
-====
-
-. Create an OpenShift Database Access catalog source using the latest add-on image repository:
-+
-.Example
-----
-$ cat <<EOF | oc apply -f -
-apiVersion: operators.coreos.com/v1alpha1
-kind: CatalogSource
-metadata:
-  name: dbaas-operator
-  namespace: openshift-marketplace
-spec:
-  sourceType: grpc
-  image: quay.io/osd-addons/dbaas-operator-index@sha256:2788a47fd0ef1ece30898c1e608050ea71036d3329b9772dbb3d1f69313f745c
-  displayName: DBaaS Operator
-EOF
-----
-
-. Verify the catalog source is added, and in a ready state:
-+
-.Example
-----
-$ oc get catalogsource dbaas-operator \
--n openshift-marketplace \
--o jsonpath='{.status.connectionState.lastObservedState} {"\n"}'
-----
-+
-IMPORTANT: Wait until the catalog source is in a `READY` state, before proceeding to the next step.
-
-. Login to the OpenShift console with a user that has administrative privileges.
-
-. In the **Administrator** perspective, expand the **Operators** navigation menu, and click **OperatorHub**.
-
-. In the filter field, type **database access**, and click the **OpenShift Database Access Operator** tile.
-
-. Click the **Install** button to show the operator details.
-
-. The default and recommended namespace for the OpenShift Database Access operator is **openshift-dbaas-operator**, click **Install** on the **Install Operator** page.
-+
-NOTE: All dependencies are automatically installed, this includes the provider account operators, and the quick-start guides.
-
-.Verification
-
-. Once the OpenShift Database Access operator successfully installs, a new navigation menu item is added, called **Data Services**.
-Expand the **Data Services** menu.
-This might take a few minutes to refresh the navigation menu.
-
-. Click **Database Access**.
-
-. On the **Database Access** home page you see an empty inventory table.
-+
-image::../images/rhoda_admin_entry_point_inventory_page.png[Database inventory landing page]
-
-.Additional resources
-
-* For additional information about OpenShift Database Access, see the _Reference Guide_.
-// End