ubicloud/rhizome
shikharbhardwaj 8ff02050a3 Add Upgrade steps to Prog::Postgres::ConvergePostgresResource
The Converge prog is now also responsible for matching the current
Postgres version to the desired version. If there is a mismatch (current
< desired), the Converge prog is launched.

Roughly, the Converge prog does the following:
1. Provisions new servers. In case of upgrades, it only provisions upto
   one new standby if no existing standby is suitable for
   upgrades.
2. Wait for the required servers to be ready.
3. Wait for the maintenance window to start.
4. Fence the primary server, and launch pg_upgrade.
5. If the upgrade is successful, replace the current primary with the
   candidate standby.

In case the upgrade fails, we delete the candidate standby and unfence the
primary to bring the database back. During the Upgrade health checking
is effectively disabled as the auto-recovery causes conflicts with the
several restarts of various versions on the candidate.
2025-10-03 11:26:08 +02:00
..
common Move metrics-collector to rhizome/common/bin 2025-05-23 12:42:17 +05:30
host Start metadata-endpoint even if the Cert is not ready 2025-10-02 16:35:27 +02:00
inference_endpoint Fix rhizome code not compatible with Ruby 3.0 2025-05-06 23:18:09 +09:00
kubernetes Bump Ubicsi to 0.3.0 2025-09-24 11:59:14 +02:00
minio/bin Enable minio.service so that we auto start after a possible reboot 2024-02-13 15:03:56 +01:00
postgres Add Upgrade steps to Prog::Postgres::ConvergePostgresResource 2025-10-03 11:26:08 +02:00
victoria_metrics/bin Add -dedup.minScrapeInterval to VictoriaMetrics command line 2025-05-08 16:47:01 +05:30
.rubocop.yml Change rhizome TargetRubyVersion to 3.0 2025-05-06 23:18:09 +09:00
Gemfile Make BUNDLE_GEMFILE=rhizome/Gemfile bundle install work from repository root 2025-05-06 23:18:09 +09:00
Gemfile.lock Add base64 to rhizome/host Gemfile 2025-04-29 16:45:24 -07:00