MongoDB blueprint without authentication

Hello @dk-do  ,

no need to modify the blueprint since you mentioned that you are not using authentication ( already existig secret ).

you just need to  create a Blueprint resource, please review the commands below:

to deploy the blueprint in kasten-io:

 curl https://raw.githubusercontent.com/kanisterio/kanister/0.73.0/examples/stable/mongodb/blueprint-v2/mongo-blueprint.yaml > mongo-blueprint.yaml

 kubectl apply -f mongo-blueprint.yaml --namespace kasten-io

Once the Blueprint is created, we will have to annotate the StatefulSet with the correct annotation to instruct K10 to use the Blueprint while performing operations on this MongoDB instance.

kubectl annotate statefulset <mongodb_satatefulset_NAME> kanister.kasten.io/blueprint='mongodb-blueprint' --namespace=mongodb-logical

P.S i suppose your secret name = statefulset name 

Here is example from my test lab:

[ahmedhagag@ahmeds-MacBook-Pro ~]$ k get statefulsets -n mongodb-logical
NAME                            READY   AGE
mongo-logical-mongodb           2/2     23m
mongo-logical-mongodb-arbiter   1/1     23m
[ahmedhagag@ahmeds-MacBook-Pro ~]$ k get secrets -n mongodb-logical
NAME                                  TYPE                                  DATA   AGE
default-token-47tg5                   kubernetes.io/service-account-token   3      23m
mongo-logical-mongodb                 Opaque                                2      23m
mongo-logical-mongodb-token-rkqk7     kubernetes.io/service-account-token   3      23m
sh.helm.release.v1.mongo-logical.v1   helm.sh/release.v1                    1      23m
[ahmedhagag@ahmeds-MacBook-Pro ~]$

Thanks!

Ahmed Hagag

In the meantime I created a workaround:

Apply a secret with dummy passwords and replace the username and password parameters in the dump_cmd in blueprint.yaml 

That is absolutely right!