You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+86-90
Original file line number
Diff line number
Diff line change
@@ -153,60 +153,25 @@ Operator support Third Party Integration.
153
153
154
154
### Step 4. Test Database as a Service (DBaaS) on OpenShift
155
155
156
-
The Atlas Operator is integrated with the [Red Hat Database-as-a-Service (DBaaS) Operator](https://github.com/RHEcosystemAppEng/dbaas-operator) which allows application developers to import database instances and connect to the databases through the [Service Binding Operator](https://github.com/redhat-developer/service-binding-operator). More information can be found [here](https://github.com/RHEcosystemAppEng/dbaas-operator#readme).
157
-
158
-
Note that both the DBaaS Operator and Atlas Operator should be installed through the [Operator Lifecyle Manager (OLM)](https://github.com/operator-framework/operator-lifecycle-manager).
156
+
The Atlas Operator is integrated with the [OpenShift Database Access Operator, a.k.a. Database-as-a-Service (DBaaS) Operator](https://github.com/RHEcosystemAppEng/dbaas-operator) which allows application developers to import database instances and connect to the databases through the [Service Binding Operator](https://github.com/redhat-developer/service-binding-operator). More information can be found [here](https://github.com/RHEcosystemAppEng/dbaas-operator#readme).
159
157
160
158
**1.** Check DBaaS Registration
161
159
162
-
If the DBaaS Operator has been deployed in the OpenShift Cluster, the Atlas Operator automatically creates a cluster level [DBaaSProvider](https://github.com/RHEcosystemAppEng/dbaas-operator/blob/main/config/crd/bases/dbaas.redhat.com_dbaasproviders.yaml) custom resource (CR) object `mongodb-atlas-registration` to automatically register itself with the DBaaS Operator.
163
-
164
-
```
165
-
apiVersion: dbaas.redhat.com/v1alpha1
166
-
kind: DBaaSProvider
167
-
metadata:
168
-
labels:
169
-
related-to: dbaas-operator
170
-
type: dbaas-provider-registration
171
-
name: mongodb-atlas-registration
172
-
spec:
173
-
connectionKind: MongoDBAtlasConnection
174
-
credentialFields:
175
-
- displayName: Organization ID
176
-
key: orgId
177
-
required: true
178
-
type: string
179
-
- displayName: Public API Key
180
-
key: publicApiKey
181
-
required: true
182
-
type: string
183
-
- displayName: Private API Key
184
-
key: privateApiKey
185
-
required: true
186
-
type: maskedstring
187
-
inventoryKind: MongoDBAtlasInventory
188
-
provider:
189
-
displayDescription: Cloud-hosted MongoDB service on AWS, Azure and Google Cloud
190
-
displayName: MongoDB Atlas Cloud Database Service
191
-
icon:
192
-
base64data: <icon image data>
193
-
mediatype: image/png
194
-
name: Red Hat DBaaS / MongoDB Atlas
195
-
```
160
+
If the DBaaS Operator has been deployed in the OpenShift Cluster, the Atlas Operator automatically creates a cluster level [DBaaSProvider](https://github.com/RHEcosystemAppEng/dbaas-operator/blob/main/config/crd/bases/dbaas.redhat.com_dbaasproviders.yaml) custom resource (CR) object `mongodb-atlas-registration` to automatically register itself with the DBaaS Operator. See file `config/dbaasprovider/dbaas_provider.yaml` for the content of the registration CR.
196
161
If the Atlas Operator is undeployed with the OLM, the above registration CR gets cleaned up automatically.
First an administrator creates a [DBaaSInventory](https://github.com/RHEcosystemAppEng/dbaas-operator/blob/main/config/crd/bases/dbaas.redhat.com_dbaasinventories.yaml) CR for MongoDB. The DBaaS Operator automatically creates a MongoDBAtlasInventory CR, and the Atlas Operator discovers the clusters and instances, and sets the result in the CR status.
165
+
First an administrator imports a provider account by creating a [DBaaSInventory](https://github.com/RHEcosystemAppEng/dbaas-operator/blob/main/config/crd/bases/dbaas.redhat.com_dbaasinventories.yaml) CR for MongoDB. The DBaaS Operator automatically creates a MongoDBAtlasInventory CR, and the Atlas Operator discovers the clusters and instances, and sets the result in the CR status.
The administrator or developer can then optionally provision an Atlas Deployment by creating a [DBaaSInstance](https://github.com/RHEcosystemAppEng/dbaas-operator/blob/main/config/crd/bases/dbaas.redhat.com_dbaasinstances.yaml) CR. The DBaaS Operator automatically creates a MongoDBAtlasInstance CR, and the Atlas Operator provisions the Atlas Deployment and sets the result in the CR status.
Now the application developer can create a [DBaaSConnection](https://github.com/RHEcosystemAppEng/dbaas-operator/blob/main/config/crd/bases/dbaas.redhat.com_dbaasconnections.yaml) CR for connection to the MongoDB database instance found, the DBaaS Operator automatically creates a MongoDBAtlasConnection CR. The Atlas Operator creates a database user in Atlas for the cluster with the default database `admin`. The Atlas Operator stores the db user credentials in a kubernetes secret, and the remaining connection information in a configmap, and then updates the MongoDBAtlasConnection CR status.
262
+
Now the application developer can create a [DBaaSConnection](https://github.com/RHEcosystemAppEng/dbaas-operator/blob/main/config/crd/bases/dbaas.redhat.com_dbaasconnections.yaml) CR for connection to the MongoDB database instance found, the DBaaS Operator automatically creates a MongoDBAtlasConnection CR. The Atlas Operator creates a database user in Atlas for the cluster with the default database `admin`. The Atlas Operator stores the db user credentials in a kubernetes secret, and the remaining connection information in a configmap and then updates the MongoDBAtlasConnection CR status.
267
263
268
264
Here is an example of MongoDBAtlasConnection CR.
269
265
```
270
-
apiVersion: dbaas.redhat.com/v1alpha1
266
+
apiVersion: dbaas.redhat.com/v1beta1
271
267
kind: MongoDBAtlasConnection
272
268
metadata:
273
269
name: test-dbaas-connection
274
270
namespace: test-namespace
275
271
ownerReferences:
276
-
- apiVersion: dbaas.redhat.com/v1alpha1
272
+
- apiVersion: dbaas.redhat.com/v1beta1
277
273
blockOwnerDeletion: true
278
274
controller: true
279
275
kind: DBaaSConnection
280
276
name: test-dbaas-connection
281
277
uid: 77193619-6ab1-43c9-acf2-a40c2cfe7703
282
278
spec:
283
-
instanceID: 12345ffbc9a90e310e642482
279
+
databaseServiceID: 12345ffbc9a90e310e642482
284
280
inventoryRef:
285
281
name: dbaas-mytest
286
282
namespace: openshift-operators
287
283
status:
288
284
conditions:
289
-
- lastTransitionTime: "2021-08-18T20:07:51Z"
285
+
- lastTransitionTime: "2023-03-28T20:06:56Z"
290
286
message: ""
291
287
reason: Ready
292
288
status: "True"
@@ -312,7 +308,7 @@ metadata:
312
308
name: atlas-db-user-5pc8b
313
309
namespace: test-namespace
314
310
ownerReferences:
315
-
- apiVersion: dbaas.redhat.com/v1alpha1
311
+
- apiVersion: dbaas.redhat.com/v1beta1
316
312
blockOwnerDeletion: false
317
313
controller: true
318
314
kind: MongoDBAtlasConnection
@@ -325,7 +321,7 @@ The corresponding generated configmap:
0 commit comments