Console (UI/API): Cluster management functionality

[vitabaks]

With the release of postgresql_cluster version 2.0, we introduced a Console (UI) designed for deploying clusters through a graphical interface. The next step is to add functionality for managing an already deployed cluster through the UI, including:

• Edit a cluster
  • Change the cluster name, description, environment, synchronous mode, etc.
• Stop/Start a cluster or a specific cluster node
  • Control the Patroni service or the VM (for cloud deployments)
• Delete a cluster
  • Remove cluster components from the server or the entire VM (for cloud deployments)
  • Note: Currently, only deleting the cluster record from the Console database has been implemented.
• Switchover/Failover, Reinit, Reload, Restart
  • Integration with the Patroni API
• Users
  • Create and edit database users
• Databases
  • Create and edit databases
• Extensions
  • Create and edit database extensions
• Parameters
  • Edit Postgres and system parameters
• Connections
  • Manage connection settings
    • Enable/disable public access to the database (for cloud deployments)
    • Configure PgBouncer connection pools
    • Manage pg_hba rules
• Backups
  • Manage database backup settings
    • Backup schedule
    • Backup retention
    • Backup tool configuration
  • Details: https://postgresql-cluster.org/docs/management/backup
• Restore a cluster
  • Restoring (PITR) or Cloning a cluster from a backup
  • Details: https://postgresql-cluster.org/docs/management/restore
• Upgrades
  • Minor and major cluster upgrade
  • Details: https://postgresql-cluster.org/docs/management/upgrades
• Cluster Scaling
  • Scaling the cluster - add Postgres node
  • Details: https://postgresql-cluster.org/docs/management/cluster-scaling

Example:

Note: Access to the Figma project with all implementation details will be provided during development.

---

Consider sponsoring the project via GitHub or Patreon

[vitabaks]

If you're interested in this feature, please consider becoming a sponsor.

The development of this feature requires sponsorship to fund developer efforts. If you're already a sponsor and are interested in this feature, please leave a comment here so we can prioritize this issue accordingly.

We also welcome contributions from those willing to dedicate their time to implement this feature on a voluntary basis. Please see the Contributing Guide for more information.