We use cookies and other similar technology to collect data to improve your experience on our site, as described in our Privacy Policy.

AppsCode
  • KubeDB

    Run Production-Grade Databases on Kubernetes

    arrow_forward
    Stash

    Backup and Recovery Solution for Kubernetes

    arrow_forward
    KubeVault

    Run Production-Grade Vault on Kubernetes

    arrow_forward
    Voyager

    Secure HAProxy Ingress Controller for Kubernetes

    arrow_forward
    ConfigSyncer

    Kubernetes Configuration Syncer

    arrow_forward
    Guard

    Kubernetes Authentication WebHook Server

    arrow_forward
    KubeDB

    KubeDB simplifies Provision, Upgrade, Scaling, Volume Expansion, Monitor, Backup, Restore for various Databases in Kubernetes on any Public & Private Cloud

    • task_altLower administrative burden
    • task_altNative Kubernetes Support
    • task_altPerformance
    • task_altAvailability and durability
    • task_altManageability
    • task_altCost-effectiveness
    • task_altSecurity
    Stash

    A complete Kubernetes native disaster recovery solution for backup and restore your volumes and databases in Kubernetes on any public and private clouds.

    • task_altDeclarative API
    • task_altBackup Kubernetes Volumes
    • task_altBackup Database
    • task_altMultiple Storage Support
    • task_altDeduplication
    • task_altData Encryption
    • task_altVolume Snapshot
    • task_altPolicy Based Backup
    KubeVault

    KubeVault is a Git-Ops ready, production-grade solution for deploying and configuring Hashicorp's Vault on Kubernetes.

    • task_altVault Kubernetes Deployment
    • task_altAuto Initialization & Unsealing
    • task_altVault Backup & Restore
    • task_altConsume KubeVault Secrets with CSI
    • task_altManage DB Users Privileges
    • task_altStorage Backend
    • task_altAuthentication Method
    • task_altDatabase Secret Engine
    Voyager

    Secure HAProxy Ingress Controller for Kubernetes

    • task_altHTTP & TCP
    • task_altSSL
    • task_altPlatform support
    • task_altHAProxy
    • task_altPrometheus
    • task_altLet's Encrypt
    configsyncer

    Kubernetes Configuration Syncer

    • task_altConfiguration Syncer
    Guard

    Kubernetes Authentication WebHook Server

    • task_altIdentity Providers
    • task_altCLI
    • task_altRBAC
  • RESOURCES
  • Webinar New
CONTACT SALES
KubeDB KubeDB
github-icon twitterx-icon
TRY NOW FREE
You are looking at the documentation of a prior release. To read the documentation of the latest release, please visit here.

New to KubeDB? Please start here.

This is an KubeDB-ops-manager only feature. Please install KubeDB ops manager to try this feature.

updating Postgres version Overview

This guide will give you an overview of how KubeDB ops manager updates the version of Postgres database.

Before You Begin

How update Process Works

The following diagram shows how KubeDB KubeDB ops manager used to update the version of Postgres. Open the image in a new tab to see the enlarged version.

Postgres update Flow
Fig: updating Process of Postgres

The updating process consists of the following steps:

  1. At first, a user creates a Postgres cr.

  2. KubeDB-Provisioner operator watches for the Postgres cr.

  3. When it finds one, it creates a StatefulSet and related necessary stuff like secret, service, etc.

  4. Then, in order to update the version of the Postgres database the user creates a PostgresOpsRequest cr with the desired version.

  5. KubeDB-ops-manager operator watches for PostgresOpsRequest.

  6. When it finds one, it Pauses the Postgres object so that the KubeDB-Provisioner operator doesn’t perform any operation on the Postgres during the updating process.

  7. By looking at the target version from PostgresOpsRequest cr, In case of major update KubeDB-ops-manager does some pre-update steps as we need old bin and lib files to update from current to target Postgres version.

  8. Then By looking at the target version from PostgresOpsRequest cr, KubeDB-ops-manager operator updates the images of the StatefulSet for updating versions.

  9. After successful upgradation of the StatefulSet and its Pod images, the KubeDB-ops-manager updates the image of the Postgres object to reflect the updated cluster state.

  10. After successful upgradation of Postgres object, the KubeDB ops manager resumes the Postgres object so that the KubeDB-provisioner can resume its usual operations.

In the next doc, we are going to show a step by step guide on updating of a Postgres database using update operation.

What's on this Page

Search
Improve This Page