percona / k8spsmdb-docs

Percona Operator for MongoDB Documentation

Percona Operator for MongoDB documentation

Introduction

Percona Operator for MongoDB automates and simplifies deploying and managing open source MongoDB clusters on Kubernetes.

This repository contains the source files for Percona Operator for MongoDB documentation. The documentation is written in Markdown markup language and is converted to HTML using MkDocs.

Contributing

Percona welcomes and encourages community contributions. See the Contribution Guide for more information.

License

Percona Server for MongoDB documentation is licensed under a Creative Commons Attribution 4.0 International License.

k8spsmdb-docs's Issues

[Bug] `mongo` client not in percona-server-mongodb:6.0.4-3

$ kubectl --kubeconfig ~/.kube/k3d-mbr run -i --rm --tty percona-client --image=percona/percona-server-mongodb:6.0.4-3 --restart=Never --env="POD_NAMESPACE=default" -- bash -il
If you don't see a command prompt, try pressing enter.
[mongodb@percona-client /]$ mongo^C
[mongodb@percona-client /]$ mongo "mongodb://databaseAdmin:[e-mail]/admin?ssl=false"
bash: mongo: command not found

[mongodb@percona-client /]$ mongo    # TABTAB
mongobridge          mongodb-healthcheck  mongoexport          mongoimport          mongos               mongostat            
mongod               mongodump            mongofiles           mongorestore         mongosh              mongotop 

so https://docs.percona.com/percona-operator-for-mongodb/cluster-wide.html#verifying-the-cluster-operation cannot be run as expected.

Outdated "Comparison with other solutions" page

I noticed that "MongoDB versions" for "MongoDB Community Edtion Operator" is out of date.
Also "Edition" is miss-spelled.
The MongoDB Community Edition Operator supports up to MongoDB 7

handling with manually created certficates a bit confusing

In https://github.com/percona/k8spsmdb-docs/blob/main/docs/TLS.md the manually created TLS-secrets are named my-cluster-name-ssl-internal and my-cluster-name-ssl.

For me it is quite confusing:

1a. There is also the ssl: key in cr.yaml, where secret-names can be defined. Is it recommended to create the secrets with the names above or use other names and define them in ssl: ?

1b. The configuration-key ssl: is not explained in the docs above.

2c. When creating my-cluster-name-ssl , this seems also be used for internal connection. So what's the use-case to define different certificates and secrets? Even with splitHorizon , it is not neccessary to create and use different certificates.

client with {{ mongodb44recommended }} is not able to connect with up-to-date-cluster

Trying to do this: https://docs.percona.com/percona-operator-for-mongodb/users.html#unprivileged-users

However, the connection from percona/percona-server-mongodb:{{ mongodb44recommended }}-client to a cluster running crVersion: 1.14.0 with image: percona/percona-server-mongodb:6.0.4-3 cannot be established. As there are confusing errors with TLS this took me hours...

This should be changed to an actual mongodb-version and mongosh

AWS doc mention GKE

At success, you will see the message that namespace/<namespace name> was created, and the context (gke_<project name>_<zone location>_<cluster name>) was modified.

in https://github.com/percona/k8spsmdb-docs/blob/main/docs/eks.md

don't know what it should be, but probably not gke_

Missing externalNodes documentation

It looks like sections related to replsets.externalNodes and sharding.configsvrReplSet.externalNodes are missing from https://github.com/percona/k8spsmdb-docs/blob/main/docs/operator.md