Overview

CloudBlue Commerce 21.0 implements a cloud-native configuration approach, where the system is deployed to a Kubernetes cluster in a cloud or on-premises.

Due to the cloud-native configuration approach, upgrading to CloudBlue Commerce 21.0 brings significant advantages:

• Dynamic infrastructure management with reduction in hardware and software expenses
• High availability at lower cost
• Optimized professional maintenance

To learn more about the deployment architecture and resource requirements of CloudBlue Commerce 21.0, see the CloudBlue Commerce 21.0 Deployment Guide.

Prerequisites

To be able to upgrade to CloudBlue Commerce 21.0, your current CloudBlue Commerce version must be 20.5. To upgrade from an earlier version, you must upgrade to version 20.5 first.

Upgrade Paths

To upgrade your CloudBlue Commerce 20.5 installation to version 21.0, follow one of these paths:

• Upgrade Path 1: From Azure VMs with Few Components in an AKS Cluster to a Cloud-Native Configuration in Azure

  In this upgrade path:

  • Your source CloudBlue Commerce 20.5 installation is:

    • System components installed in Azure VMs (OSS MN, BSS application node, and so on)

    • System components installed in an AKS cluster

    • System databases placed in Azure VMs or in the Azure Database for PostgreSQL service

    • DNS services installed in Azure VMs

    • Application endpoints installed in Azure VMs

  • Your destination CloudBlue Commerce 21.0 installation is:

    • System components installed in a new AKS cluster

    • System databases placed in the same Azure VMs or in the Azure Database for PostgreSQL service

    • DNS services installed in the same Azure VMs

    • Application endpoints installed in the same Azure VMs

• Upgrade Path 2: From Azure VMs to a Cloud-Native Configuration in Azure

  In this upgrade path:

  • Your source CloudBlue Commerce 20.5 installation is:

    • System components installed in Azure VMs (OSS MN, BSS application node, and so on)

    • System databases placed in Azure VMs or in the Azure Database for PostgreSQL service

    • DNS services installed in Azure VMs

    • Application endpoints installed in Azure VMs

  • Your destination CloudBlue Commerce 21.0 installation is:

    • System components installed in an AKS cluster

    • System databases placed in the same Azure VMs or in the Azure Database for PostgreSQL service

    • DNS services installed in the same Azure VMs

    • Application endpoints installed in the same Azure VMs

• Upgrade Path 3: From a Datacenter with Few Components in a Local Kubernetes Cluster to a Cloud-Native Configuration in a Datacenter

  In this upgrade path:

  • Your source CloudBlue Commerce 20.5 installation is:

    • System components installed on physical or virtual servers (OSS MN, BSS application server, and so on)

    • System components installed in a Kubernetes cluster

    • System databases placed on physical or virtual servers

    • DNS services installed on physical or virtual servers

    • Application endpoints installed on physical or virtual servers

  • Your destination CloudBlue Commerce 21.0 installation is:

    • System components installed in a Kubernetes cluster

    • System databases placed on the same physical or virtual servers

    • DNS services installed on the same physical or virtual servers

    • Application endpoints installed on the same physical or virtual servers

• Upgrade Path 4: From a Classic Deployment in a Datacenter to a Cloud-Native Configuration in a Datacenter

  In this upgrade path:

  • Your source CloudBlue Commerce 20.5 installation is:

    • System components installed on physical or virtual servers (OSS MN, BSS application server, and so on)

    • System databases placed on physical or virtual servers

    • DNS services installed on physical or virtual servers

    • Application endpoints installed on physical or virtual servers

  • Your destination CloudBlue Commerce 21.0 installation is:

    • System components installed in a Kubernetes cluster

    • System databases placed on the same physical or virtual servers

    • DNS services installed on the same physical or virtual servers

    • Application endpoints installed on the same physical or virtual servers

• Upgrade Path 5: From a Classic Configuration in a Datacenter to a Cloud-Native Configuration in Azure (with Database Migration to Azure Database for PostgreSQL)

  In this upgrade path:

  • Your source CloudBlue Commerce 20.5 installation is:

    • System components installed on physical or virtual servers (OSS MN, BSS application server, and so on)

    • (Optional) System components installed in a Kubernetes cluster

    • System databases placed on physical or virtual servers

    • DNS services installed on physical or virtual servers

    • Application endpoints installed on physical or virtual servers

  • Your destination CloudBlue Commerce 21.0 installation is:

    • System components installed in an AKS cluster

    • System databases placed in the Azure Database for PostgreSQL service

    • DNS services installed in Azure VMs

    • Application endpoints installed in Azure VMs