Paul Seymour
Paul Seymour
Hi, Thanks for looking. The creds don't have special characters in them. I tried building from your branch and I got this error:- ``` error occurred during connection handshake: x509:...
I added TLS stuff and now it's working - well making a connection and getting some data back. I don't get a `cluster` label (which the dashboard expect), nor do...
My secret and webhook don't have any values for `caBundle` and I get this error. It's a clean deployment to a new cluster ? UPDATE: I deleted the controller pod...
Well for what it's worth I have just got hit by this also.
Thanks. No it cannot (same error as above which explains it !). Which is odd as I deployed the Mongo instance with the Operator with the admin account to have...
Thanks. Just using the Community Operator from https://github.com/mongodb/mongodb-kubernetes-operator Then my manifest for that is:- ``` --- apiVersion: mongodbcommunity.mongodb.com/v1 kind: MongoDBCommunity metadata: name: mongodb spec: members: 3 type: ReplicaSet version: "4.2.7"...
Interesting I create another user manually from a mongo shell and use that in the connection I now get:- ```Welcome to mongo-express ------------------------ (node:8) [MONGODB DRIVER] Warning: Current Server Discovery...
I have the same problem on the 2.3.0 RC1 as well
I am still seeing this with `2.5.0-rc1`
Yes it appears to be the case that a new SA is created. Rather makes the use of private registeries impossible.