Skip to content

Commit 6598894

Browse files
committed
resolve conflict
Signed-off-by: Bonusree <[email protected]>
1 parent bb8bc0d commit 6598894

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

docs/guides/mongodb/initialization/gitsync.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ The following YAML manifest shows an example `MongoDB` object configured with `g
3939
apiVersion: kubedb.com/v1
4040
kind: MongoDB
4141
metadata:
42-
name: rs
42+
name: mg-git
4343
namespace: demo
4444
spec:
4545
init:
@@ -68,7 +68,7 @@ spec:
6868
```
6969
```bash
7070
kubectl create -f https://github.com/kubedb/docs/raw/{{< param "info.version" >}}/docs/examples/mongodb/initialization/git-sync-public.yaml
71-
MongoDB.kubedb.com/rs created
71+
MongoDB.kubedb.com/mg-git created
7272
```
7373

7474
The `git-sync` container has two required flags:
@@ -79,21 +79,21 @@ The `git-sync` container has two required flags:
7979

8080
> To know more about `git-sync` configuration visit this [link](https://github.com/kubernetes/git-sync).
8181
82-
Now, wait until `rs` has status `Ready`. i.e,
82+
Now, wait until `mg-git` has status `Ready`. i.e,
8383

8484
```bash
8585
$ kubectl get mg -n demo
8686
NAME VERSION STATUS AGE
87-
rs 8.0.4 Ready 49m
87+
mg-git 8.0.4 Ready 49m
8888

8989
```
9090

9191
Next, we will connect to the MongoDB database and verify the data inserted from the `*.js` script stored in the Git repository.
9292

9393
```bash
94-
$ kubectl exec -it -n demo rs-0 -- bash
94+
$ kubectl exec -it -n demo mg-git-0 -- bash
9595
Defaulted container "mongodb" out of: mongodb, copy-config (init), git-sync (init)
96-
mongodb@rs-0:/$ mongosh -u root -p $<your_mongodb_root_password>
96+
mongodb@mg-git-0:/$ mongosh -u root -p $<your_mongodb_root_password>
9797
Current Mongosh Log ID: 6900695d231f7a9e99ce5f46
9898
Connecting to: mongodb://<credentials>@127.0.0.1:27017/?directConnection=true&serverSelectionTimeoutMS=2000&appName=mongosh+2.5.8
9999
Using MongoDB: 8.0.4
@@ -163,7 +163,7 @@ The following YAML manifest provides an example of a `MongoDB` resource configur
163163
apiVersion: kubedb.com/v1
164164
kind: MongoDB
165165
metadata:
166-
name: rs
166+
name: mg-git-ssh
167167
namespace: demo
168168
spec:
169169
init:
@@ -204,7 +204,7 @@ spec:
204204
205205
```bash
206206
kubectl create -f https://github.com/kubedb/docs/raw/{{< param "info.version" >}}/docs/examples/mongodb/initialization/git-sync-ssh.yaml
207-
MongoDB.kubedb.com/rs created
207+
MongoDB.kubedb.com/mg-git-ssh created
208208
```
209209

210210
Here,
@@ -217,9 +217,9 @@ Once the database reaches the `Ready` state, you can verify the data using the m
217217
Next, we will connect to the MongoDB database and verify the data inserted from the `*.js` script stored in the Git repository.
218218

219219
```bash
220-
$ kubectl exec -it -n demo rs-0 -- bash
220+
$ kubectl exec -it -n demo mg-git-ssh-0 -- bash
221221
Defaulted container "mongodb" out of: mongodb, copy-config (init), git-sync (init)
222-
mongodb@rs-0:/$ mongosh -u root -p 'tQ;c(ykM_T_EbLKS'
222+
mongodb@mg-git-ssh-0:/$ mongosh -u root -p 'tQ;c(ykM_T_EbLKS'
223223
Current Mongosh Log ID: 6900695d231f7a9e99ce5f46
224224
Connecting to: mongodb://<credentials>@127.0.0.1:27017/?directConnection=true&serverSelectionTimeoutMS=2000&appName=mongosh+2.5.8
225225
Using MongoDB: 8.0.4
@@ -273,7 +273,7 @@ The following YAML manifest shows an example:
273273
apiVersion: kubedb.com/v1
274274
kind: MongoDB
275275
metadata:
276-
name: rs
276+
name: mg-git-pat
277277
namespace: demo
278278
spec:
279279
init:
@@ -315,7 +315,7 @@ spec:
315315
316316
```bash
317317
kubectl create -f https://github.com/kubedb/docs/raw/{{< param "info.version" >}}/docs/examples/mongodb/initialization/git-sync-pat.yaml
318-
MongoDB.kubedb.com/rs created
318+
MongoDB.kubedb.com/mg-git-pat created
319319
```
320320
The `git-sync` container has two required flags:
321321
- `--repo` – specifies the remote Git repository to sync.
@@ -329,7 +329,7 @@ Once the database reaches the `Ready` state, you can verify the data using the m
329329
```yaml
330330
$ kubectl get mg -n demo
331331
NAME VERSION STATUS AGE
332-
rs 8.0.4 Ready 38m
332+
mg-git-pat 8.0.4 Ready 38m
333333

334334
```
335335

@@ -338,6 +338,6 @@ rs 8.0.4 Ready 38m
338338
To clean up the Kubernetes resources created by this tutorial, run:
339339

340340
```bash
341-
$ kubectl delete MongoDB -n demo rs
341+
$ kubectl delete MongoDB -n demo mg-git mg-git-ssh mg-git-pat
342342
$ kubectl delete ns demo
343343
```

0 commit comments

Comments
 (0)