Databases
Updated on October 27, 2026
Databases
Webgune provisions databases directly inside Kubernetes, with persistent storage (PVC): data survives restarts and image updates.
Choosing an engine
| Engine | Port | Typical use case | Guide |
|---|---|---|---|
| PostgreSQL | 5432 | relational applications, rich ORMs | PostgreSQL |
| MySQL | 3306 | WordPress, Laravel, PHP in general | MySQL |
| MariaDB | 3306 | MySQL fork, same drivers | MariaDB |
| MongoDB | 27017 | JSON documents, flexible schema | MongoDB |
| Redis | 6379 | cache, sessions, queues | Redis |
Creating a database
- + New service → Database.
- Choose the engine.
- Name the database.
- The password is generated automatically (customizable if needed).
- Create: the database is ready within seconds.
Two ways to connect
- Internal URL: for services within the same project, via the cluster's internal DNS. This is the default choice.
- Public URL (NodePort): for access from outside (local machine, graphical tool). Must be explicitly enabled via Expose publicly in the Database tab.
Built-in SQL interface
The Database tab includes a phpMyAdmin-like explorer: a list of tables with their structure, and a query editor (Ctrl+Enter to execute).
Backups
The service's Backups tab covers both needs, manual and scheduled. See Backups and restore for the details. In short: a dump exports the contents of the database, a snapshot copies the whole volume, and a backup is restored from the same list.
Turn scheduling on before you go to production. It runs daily by default. Without a backup, an accidental deletion cannot be undone.