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
// Optional version of MongoDB Search component (mongot). If not set, then the operator will set the most appropriate version of MongoDB Search.
30
31
// +optional
31
32
Versionstring`json:"version"`
33
+
// MongoDB database connection details from which MongoDB Search will synchronize data to build indexes.
32
34
// +optional
33
35
Source*MongoDBSource`json:"source"`
36
+
// StatefulSetSpec which the operator will apply to the MongoDB Search StatefulSet at the end of the reconcile loop. Use to provide necessary customizations,
37
+
// which aren't exposed as fields in the MongoDBSearch.spec.
-**Kubernetes cluster**: A running Kubernetes cluster (e.g., Minikube, Kind, GKE, EKS, AKS) with kubeconfig available locally.
10
10
-**kubectl**: The Kubernetes command-line tool, configured to communicate with your cluster.
11
11
-**Helm**: The package manager for Kubernetes, used here to install the MongoDB Kubernetes Operator.
12
12
-**Bash 5.1+**: All shell commands in this guide are intended to be run in Bash. Scripts in this guide are automatically tested on Linux with Bash 5.1.
@@ -27,15 +27,18 @@ Download or copy the content of `env_variables.sh`:
This command installs the operator in the `mongodb` namespace (creating it if it doesn't exist) and names the release `community-operator`.
71
-
72
-
### 4. Configure Pull Secret for MongoDB Community Search
73
-
74
-
To use MongoDB Search, your Kubernetes cluster needs to pull the necessary container images. This step creates a Kubernetes secret named `community-private-preview-pullsecret`. This secret stores the credentials required to access the image repository for MongoDB Search. The script then patches the `mongodb-kubernetes-database-pods` service account to include this pull secret, allowing pods managed by this service account to pull the required images.
echo"ServiceAccount mongodb-kubernetes-database-pods has been patched: "
101
-
102
-
kubectl get --context "${K8S_CLUSTER_0_CONTEXT_NAME}" -n "${MDB_NAMESPACE}" -o yaml sa mongodb-kubernetes-database-pods
103
-
```
104
-
This script creates a `community-private-preview-pullsecret` secret in your Kubernetes namespace and associates it with the service account used for MongoDB pods.
105
-
106
-
### 5. Verify Pull Secret Configuration
107
-
108
-
Confirm that the `community-private-preview-pullsecret` has been successfully added to the `mongodb-kubernetes-database-pods` service account. This ensures that Kubernetes can authenticate with the container registry when pulling images for MongoDB Search pods.
Ensure these secrets are created in the same namespace where you plan to deploy MongoDB.
143
99
144
100
### 7. Create MongoDB Community Resource
145
101
146
-
Now, deploy MongoDB Community by creating a `MongoDBCommunity` custom resource named `mdbc-rs`. This resource definition instructs the MongoDB Kubernetes Operator to configure a MongoDB replica set with 3 members, running version 8.0.6. MongoDB Community Search is supported only from MongoDB Community Server version 8.0. It also defines CPU and memory resources for the `mongod` and `mongodb-agent` containers, and sets up two users (`admin-user` and `search-user`) with their respective roles and password secrets. User `search-user` will be used to restore, connect and perform search queries on the `sample_mflix` database.
102
+
Now, deploy MongoDB Community by creating a `MongoDBCommunity` custom resource named `mdbc-rs`. This resource definition instructs the MongoDB Kubernetes Operator to configure a MongoDB replica set with 3 members, running version 8.0.10. MongoDB Community Search is supported only from MongoDB Community Server version 8.0.10. It also defines CPU and memory resources for the `mongod` and `mongodb-agent` containers, and sets up three users:
103
+
*`mdb-user` - a regular user used to that will perform restore of `sample_mflix` database and execute search queries.
104
+
*`search-sync-source` - user that MongoDB Search is using to connect to MongoDB database in order to manage and build indexes. This user uses `searchCoordinator` role, which for MongoDB <8.2 is created automatically by the operator.
105
+
*`admin-user` and ``) with their respective roles and password secrets. User `search-user` will be used to restore, connect and perform search queries on the `sample_mflix` database.
Once your MongoDB deployment is ready, enable Search capabilities by creating a `MongoDBSearch` custom resource, also named `mdbc-rs` to associate it with the MongoDB instance. This resource specifies the CPU and memory resource requirements for the search nodes.
224
198
225
-
Note: Private preview of MongoDB Community Search comes with some limitations, and it is not suitable for production use:
226
-
* TLS cannot be enabled in MongoDB Community deployment (MongoD communicates with MongoT with plain text).
227
-
* Only one node of search node is supported (load balancing not supported)
199
+
Note: Public Preview of MongoDB Community Search comes with some limitations, and it is not suitable for production use:
200
+
* Only one instance of the search node is supported (load balancing is not supported)
Copy file name to clipboardExpand all lines: docs/community-search/quick-start/README.md.j2
+6-4Lines changed: 6 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,10 @@ Ensure these secrets are created in the same namespace where you plan to deploy
63
63
64
64
### 7. Create MongoDB Community Resource
65
65
66
-
Now, deploy MongoDB Community by creating a `MongoDBCommunity` custom resource named `mdbc-rs`. This resource definition instructs the MongoDB Kubernetes Operator to configure a MongoDB replica set with 3 members, running version 8.0.6. MongoDB Community Search is supported only from MongoDB Community Server version 8.0. It also defines CPU and memory resources for the `mongod` and `mongodb-agent` containers, and sets up two users (`admin-user` and `search-user`) with their respective roles and password secrets. User `search-user` will be used to restore, connect and perform search queries on the `sample_mflix` database.
66
+
Now, deploy MongoDB Community by creating a `MongoDBCommunity` custom resource named `mdbc-rs`. This resource definition instructs the MongoDB Kubernetes Operator to configure a MongoDB replica set with 3 members, running version 8.0.10. MongoDB Community Search is supported only from MongoDB Community Server version 8.0.10. It also defines CPU and memory resources for the `mongod` and `mongodb-agent` containers, and sets up three users:
67
+
* `mdb-user` - a regular user used to that will perform restore of `sample_mflix` database and execute search queries.
68
+
* `search-sync-source` - user that MongoDB Search is using to connect to MongoDB database in order to manage and build indexes. This user uses `searchCoordinator` role, which for MongoDB <8.2iscreatedautomaticallybytheoperator.
@@ -83,9 +86,8 @@ After applying the `MongoDBCommunity` custom resource, the operator begins deplo
83
86
84
87
Once your MongoDB deployment is ready, enable Search capabilities by creating a `MongoDBSearch` custom resource, also named `mdbc-rs` to associate it with the MongoDB instance. This resource specifies the CPU and memory resource requirements for the search nodes.
85
88
86
-
Note: Private preview of MongoDB Community Search comes with some limitations, and it is not suitable for production use:
87
-
* TLS cannot be enabled in MongoDB Community deployment (MongoD communicates with MongoT with plain text).
88
-
* Only one node of search node is supported (load balancing not supported)
89
+
Note: Public Preview of MongoDB Community Search comes with some limitations, and it is not suitable for production use:
90
+
* Only one instance of the search node is supported (load balancing is not supported)
0 commit comments