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.

Updating Redis version Overview

This guide will give you an overview on how KubeDB Enterprise operator upgrade the version of Redis database.

Before You Begin

How Update Version Process Works

The following diagram shows how KubeDB Enterprise operator used to upgrade the version of Redis. Open the image in a new tab to see the enlarged version.

  Update Version Process of Redis
Fig: Update Version Process of Redis

The updating process consists of the following steps:

  1. At first, a user creates a Redis/RedisSentinel Custom Resource (CR).

  2. KubeDB Community operator watches the Redis and RedisSentinel CR.

  3. When the operator finds a Redis/RedisSentinel CR, it creates required number of StatefulSets and related necessary stuff like appbinding, services, etc.

  4. Then, in order to upgrade the version of the Redis database the user creates a RedisOpsRequest CR with the desired version.

  5. Then, in order to upgrade the version of the RedisSentinel database the user creates a RedisSentinelOpsRequest CR with the desired version.

  6. KubeDB Enterprise operator watches the RedisOpsRequest and RedisSentinelOpsRequest CR.

  7. When it finds a RedisOpsRequest CR, it halts the Redis object which is referred from the RedisOpsRequest. So, the KubeDB Community operator doesn’t perform any operations on the Redis object during the upgrading process.

  8. When it finds a RedisSentinelOpsRequest CR, it halts the RedisSentinel object which is referred from the RedisSentinelOpsRequest. So, the KubeDB Community operator doesn’t perform any operations on the RedisSentinel object during the upgrading process.

  9. By looking at the target version from RedisOpsRequest/RedisSentinelOpsRequest CR, KubeDB Enterprise operator updates the images of all the StatefulSets.

  10. After successfully updating the StatefulSets and their Pods images, the KubeDB Enterprise operator updates the image of the Redis/RedisSentinel object to reflect the updated state of the database.

  11. After successfully updating of Redis/RedisSentinel object, the KubeDB Enterprise operator resumes the Redis/RedisSentinel object so that the KubeDB Community operator can resume its usual operations.

In the next doc, we are going to show a step-by-step guide on upgrading of a Redis database using upgrade operation.

Next Steps

What's on this Page

Search
Improve This Page