How to deploy mongodb.com_v1_mongodb_scram_cr.yaml successfully about mongodb-kubernetes-operator HOT 10 CLOSED

Yes waiting for this also :)

from mongodb-kubernetes-operator.

Hello Friends!

Are we close to the release of this feature? We are really looking forward for the same?

Thank you

from mongodb-kubernetes-operator.

Hi @hemantkathuria

The mongodb.com_v1_mongodb_scram_cr.yaml CR file only partially configures SCRAM. This feature is still a work in progress and so it won't be possible to configure SCRAM users until that work is complete, which should be within the next week or two (at which point there will be more documentation available for how to configure your users).

Regarding the unbound immediate PersistentVolumeClaims error, this could be harder to debug.

Could you provide more information about the storageclass you're using, (kubectl describe storageclass <class>) and also the output of kubectl describe pvc <pvc-with-issue>.

from mongodb-kubernetes-operator.

Hi @hemantkathuria

The mongodb.com_v1_mongodb_scram_cr.yaml CR file only partially configures SCRAM. This feature is still a work in progress and so it won't be possible to configure SCRAM users until that work is complete, which should be within the next week or two (at which point there will be more documentation available for how to configure your users).

Regarding the unbound immediate PersistentVolumeClaims error, this could be harder to debug.

Could you provide more information about the storageclass you're using, (kubectl describe storageclass <class>) and also the output of kubectl describe pvc <pvc-with-issue>.

Thank you very much for the quick response. Looking forward for the SCRAM support. Please find below the output of the asked commands. Also, please note, i was able to install once using "mongodb.com_mongodb_crd.yaml". But when I tried "mongodb.com_v1_mongodb_scram_cr.yaml" I faced the issues.

kubectl describe storageclass default

`

Name: default
IsDefaultClass: Yes
Annotations: kubectl.kubernetes.io/last-applied-configuration={"allowVolumeExpansion":true,"apiVersion":"storage.k8s.io/v1beta1","kind":"StorageClass","metadata":{"annotations":{"storageclass.beta.kubernetes.io/is-default-class":"true"},"labels":{"kubernetes.io/cluster-service":"true"},"name":"default"},"parameters":{"cachingmode":"ReadOnly","kind":"Managed","storageaccounttype":"StandardSSD_LRS"},"provisioner":"kubernetes.io/azure-disk"}
,storageclass.beta.kubernetes.io/is-default-class=true
Provisioner: kubernetes.io/azure-disk
Parameters: cachingmode=ReadOnly,kind=Managed,storageaccounttype=StandardSSD_LRS
AllowVolumeExpansion: True
MountOptions:
ReclaimPolicy: Delete
VolumeBindingMode: Immediate
Events:

kubectl describe pvc kubectl describe pvc data-volume-example-scram-mongodb-0

Name: data-volume-example-scram-mongodb-0
Namespace: default
StorageClass: default
Status: Bound
Volume: pvc-cfae6a47-56a8-4e9b-b1be-3614d5f43a94
Labels: app=example-scram-mongodb-svc
Annotations: pv.kubernetes.io/bind-completed: yes
pv.kubernetes.io/bound-by-controller: yes
volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/azure-disk
Finalizers: [kubernetes.io/pvc-protection]
Capacity: 10Gi
Access Modes: RWO
VolumeMode: Filesystem
Mounted By: example-scram-mongodb-0
Events:

from mongodb-kubernetes-operator.

Hi @chatton Is this feature released yet?
Thanks

from mongodb-kubernetes-operator.

I just tried to create a db with TLS but it objecting saying i needed to setup users first?

from mongodb-kubernetes-operator.

I just tried the release v0.2.0 which include users in the file mongodb.com_v1_mongodb_cr.yaml and it does not works. Got warn: WARN mongodb/replica_set_controller.go:174 error creating automation config config map: Secret "digital-factory-mongodb-mdfdb-admin-scram-credentials" not found

I have changed the name of deploy from example-mongodb to digital-factory-mongodb and user name from my-user to mdfdb-admin

from mongodb-kubernetes-operator.

Hello @naddame, can you please create a new issue and paste the yaml file you used and the command you used to create the secret? Thanks!

Hi @pixie79, can you please open a new issue and gives us a bit more information about how you tried to set up a db with TLS? Thanks!

from mongodb-kubernetes-operator.

This issue is labeled as stale because it has been open for more than 30 days with no activity. Remove stale label or comment or this will be closed in a few days.

from mongodb-kubernetes-operator.

This issue was closed because it became stale and did not receive further updates. If the issue is still affecting you, please re-open it, or file a fresh Issue with updated information.

from mongodb-kubernetes-operator.