Skip to content

Release v3.0.0

Latest
Latest
Compare
Choose a tag to compare
@SIGHUP-C-3PO SIGHUP-C-3PO released this 27 Nov 16:34
· 1 commit to main since this release
v3.0.0
1b48412
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Disaster recovery Core Module Release 3.0.0

Welcome to the latest release of the DR module of Kubernetes Fury Distribution maintained by team SIGHUP.

This latest release upgrades the components in the module to their latest stable release, and it's considered a major release since we are changing the default backup method to kopia and enabling by default the EnableCSI feature.

A new component snapshot-controller has been added, which allows the volumes data to be backed up to a pre-defined backup storage in a consistent manner.

Component Images 🚢

Component Supported Version Previous Version
velero v1.15.0 1.14.0
velero-plugin-for-aws v1.11.0 1.10.0
velero-plugin-for-microsoft-azure v1.11.0 1.10.0
velero-plugin-for-gcp v1.11.0 1.10.0
snapshot-controller v8.0.1 -

Please refer to the individual release notes to get a detailed information on each release.

Features 💥

Upgrade Guide 🦮

🚨 Requirement 🚨

Before to upgrade the Velero module to v3.0.0, check if the snapshot-controller is already installed on your cluster.

If it is not, you can install the snapshot-controller package.

Run from the snapshot-controller folder:

# Install snapshot-controller
kustomize build . | kubectl apply -f -

Process

To upgrade this module from v2.4.x to v3.0.0, you need to download this new version and then:

  1. Upgrade Velero CRDs
# Upgrade CRDs
kubectl apply -f katalog/velero-base/crds.yaml
  1. Check if the snapshot-controller is already installed on your cluster:
# Check if snapshot-controller CRDs are installed
kubectl get crds | grep -E 'volumesnapshots|volumesnapshotclasses|volumesnapshotcontents'
  1. Upgrade Velero
# Upgrade Velero
kustomize build katalog/velero/velero-aws | kubectl apply -f -
# Or
kustomize build katalog/velero/velero-gcp | kubectl apply -f -
# Or
kustomize build katalog/velero/velero-azure | kubectl apply -f -
# Or, if the cluster is on-premise remove the minio-setup job first
kubectl delete job -n kube-system minio-setup
kustomize build katalog/velero/velero-on-prem | kubectl apply -f -
Assets 5
Loading