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
Hi, as I saw that it's a drop in replacement for it, I'm about to swap MongoDb community for the Percona psmdb-db in my Kubernetes cluster and I need a bit of clarifications about the Chart's values.
I need to specify 2 PVC ( one for data and one for logs) per pod but I see only parameters for one replsets[0].volumeSpec.pvc. How do I add more than one if it's possible?
In the chart's value file I don't see any replsets[0].podSecurityContext, while I do see it for nonvotingand sharded so I guess it's just not present in the chart's Values file but available as a parameter to set.
How to specify a db name? It will be the db name in the driver's connection string..so I 'd need to know what db name to use.
Is backup remote storage possible on GCP for Firebase storage buckets?
Is namespace definable only at chart install or is there a parameter to specify it?
Many thanks.
At the moment the manifest for MongoDBCommunity resource is:
sorry it sat so long here.
I would think that forums.percona.com would be a much better place to discuss it. Anyway, answering your questions/concerns one by one:
It is not possible yet, but we have it in our roadmap.
We do support it, but indeed it is not mentioned properly in the default cr.yaml and not properly documented.
You can use it as follows:
Hi, as I saw that it's a drop in replacement for it, I'm about to swap MongoDb community for the Percona psmdb-db in my Kubernetes cluster and I need a bit of clarifications about the Chart's values.
replsets[0].volumeSpec.pvc
. How do I add more than one if it's possible?replsets[0].podSecurityContext
, while I do see it fornonvoting
andsharded
so I guess it's just not present in the chart's Values file but available as a parameter to set.Many thanks.
At the moment the manifest for MongoDBCommunity resource is:
The text was updated successfully, but these errors were encountered: