Skip to content

Databases

Managed MongoDB on your own cluster

MongoDB managed by the Percona operator, run as a replica set with a volume per member.

Created inside a project, beside the apps that use it. Each project gets its own instance, storage and credentials.

01What it does

MongoDB, run for you

MongoDB 7.0 or 8.0 on the Percona operator, as a replica set.

A document database run the way MongoDB wants to be run: as a replica set, even with one member, so growing to three later is a setting rather than a migration. Each member gets its own volume, and bound apps receive a MONGODB_URL beside the host, port, database, username and password.

Three members give automatic failover and need three schedulable nodes. The replica set hands clients the members' internal addresses to follow, which is why it has no public port: a connection from outside the cluster would be told to go somewhere it cannot reach.

02Options

What you choose

What the console asks when you create it, in the catalog's own numbers. Anything marked chosen once cannot change without creating a new instance.

Sizes
small 0.5 CPU / 1Gi, medium 1 / 2Gi, large 2 / 4Gi per member
Storage
10Gi per member by default; grows later if the storage class supports expansion
Versions
7.0 or 8.0 (default), chosen once
Members
1, or 3 for automatic failover; chosen once
Pause
Yes; the volumes are kept
Public port
None; a replica set cannot be reached through one

03Binding

What your app receives

Bind it to an app and these arrive as environment variables. The values are generated once into a secret and reach the app from there, rather than as something you copy.

  • MONGODB_HOST
  • MONGODB_PORT
  • MONGODB_DATABASE
  • MONGODB_USERNAME
  • MONGODB_PASSWORD
  • MONGODB_URL

04Adding it

Add MongoDB to a project

The same four steps as every service in the catalog.

  1. 01Open a project and go to Services.
  2. 02Pick it from the catalog and choose its options. Only the size is required; everything else has a default.
  3. 03Create it. Anyport installs it into the project's namespace, generates its credentials into a secret there, and tracks its health.
  4. 04Bind it to an app. The connection details arrive as environment variables, and rotating the credential never means editing an app.