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
    Kubeform

    Provision cloud resources using Kubernetes CRDs & Terraform

    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
    Kubeform

    Provision cloud resources
    using Kubernetes CRDs
    & Terraform

    • task_altNative Kubernetes Support
    • task_altBuilt on Terrafrom
    • task_altInfrastructure as Code
    • task_altSupports Multiple Cloud Platform
    • task_altUnleash Developer Velocity
  • Guard

    Kubernetes Authentication WebHook Server

    • task_altIdentity Providers
    • task_altCLI
    • task_altRBAC
    Kubed

    Kubernetes cluster manager daemon

    • task_altDisaster Recovery
    • task_altEvent Forwarder
    • task_altConfiguration Syncer
    • task_altRecycle Bin
    • task_altEvent Notifiers
    • task_altJanitor
    Pharmer

    Kubernetes Cluster Manager using Kubeadm & Cluster API

    • task_altKubeadm
    • task_altPlatform Support
    • task_altKubernetes Certification
    Swift

    Ajax friendly Helm Tiller Proxy

    • task_altAPI Support
    • task_altgRPC Gateway
    • task_altJS Client
    Searchlight

    Alerts for Kubernetes

    • task_altMonitor Kubernetes
    • task_altIcinga 2
    • task_altNotifier Support
  • Webinar New
Voyager Voyager
github-icon twitter-icon
TRY NOW FREE
  • Welcome
  • Concepts
  • Setup
  • Ingress
    arrow_forward
    Cert Manager
    arrow_forward
  • Voyager Operator
    arrow_forward
    Voyager CLI
    arrow_forward

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

Upgrading Voyager

This guide will show you how to upgrade various Voyager components. Here, we are going to show how to upgrade from an old Voyager version to the new version, how to migrate between the enterprise edition and community edition, and how to update the license, etc.

Upgrading Voyager from v2021.x.x to v2023.05.16

In order to upgrade from Voyager v2021.x.x to v2023.05.16, please follow the following steps.

Please note that since v2021.09.16, we recommend installing Voyager operator in the voyager namespace. The upgrade instructions on this page assumes so. If you have currently installed the operator in a different namespace like kube-system, either follow the instructions with appropriate updates, or first uninstall the existing operator and then reinstall in the voyager namespace.

1. Update Voyager Catalog CRDs

Helm does not upgrade the CRDs bundled in a Helm chart if the CRDs already exist. So, to upgrade the Voyager catalog CRD, please run the command below:

kubectl apply -f https://github.com/voyagermesh/installer/raw/v2023.05.16/crds/voyager-crds.yaml

2. Upgrade Voyager Operator

Now, upgrade the Voyager helm chart using the following command. You can find the latest installation guide here.

helm upgrade voyager-operator appscode/voyager \
  --version v2023.05.16 \
  --namespace voyager \
  --set cloudProvider=$provider \
  --set-file license=/path/to/the/license.txt

Migration Between Community Edition and Enterprise Edition

Voyager supports seamless migration between community edition and enterprise edition. You can run the following commands to migrate between them.

Using Helm 3

From Community Edition to Enterprise Edition:

In order to migrate from Voyager community edition to Voyager enterprise edition, please run the following command,

helm upgrade voyager-operator appscode/voyager \
  --namespace voyager \
  --reuse-values \
  --set-file license=/path/to/voyager-enterprise-license.txt

From Enterprise Edition to Community Edition:

In order to migrate from Voyager enterprise edition to Voyager community edition, please run the following command,

helm upgrade voyager-operator appscode/voyager \
  --namespace voyager \
  --reuse-values \
  --set-file license=/path/to/voyager-community-license.txt

Using YAML (with helm 3)

From Community Edition to Enterprise Edition:

In order to migrate from Voyager community edition to Voyager enterprise edition, please run the following command,

# Install Voyager enterprise edition
helm template voyager appscode/voyager \
  --namespace voyager --create-namespace \
  --version v2023.05.16 \
  --set cleaner.skip=true \
  --set-file license=/path/to/voyager-enterprise-license.txt | kubectl apply -f -

From Enterprise Edition to Community Edition:

In order to migrate from Voyager enterprise edition to Voyager community edition, please run the following command,

# Install Voyager community edition
helm template voyager appscode/voyager \
  --namespace voyager --create-namespace \
  --version v2023.05.16 \
  --set cleaner.skip=true \
  --set-file license=/path/to/voyager-community-license.txt | kubectl apply -f -

Updating License

Voyager support updating license without requiring any re-installation. Voyager creates a Secret named <helm release name>-license with the license file. You just need to update the Secret. The changes will propagate automatically to the operator and it will use the updated license going forward.

Follow the below instructions to update the license:

  • Get a new license and save it into a file.
  • Then, run the following upgrade command based on your installation.

Using Helm 3

# detect current version
helm ls -A | grep voyager

# update license key keeping the current version
helm upgrade voyager-operator appscode/voyager --version=<cur_version> \
  --namespace voyager \
  --reuse-values \
  --set-file license=/path/to/new/license.txt

Using YAML (with helm 3)

# detect current version
helm ls -A | grep voyager

# update license key keeping the current version
helm template voyager appscode/voyager --version=<cur_version> \
  --namespace voyager --create-namespace \
  --set cleaner.skip=true \
  --set-file license=/path/to/new/license.txt | kubectl apply -f -

What's on this Page

Search
Improve This Page