test(E2E): refactor AKS backup tests to use native blob containers for Barman Cloud integration

When run on Azure, the backup and restore tests now include a test using Azure Blob Storage, in
addition to the one using Minio.

Co-authored-by: Gabriele Quaresima <gabriele.quaresima@enterprisedb.com>
Co-authored-by: Francesco Canovai <francesco.canovai@enterprisedb.com>

Author: 3 people

docs/src/e2e.md

@@ -37,8 +37,10 @@ and the following suite of E2E tests are performed on that cluster:
 * Manage PostgreSQL configuration changes;
 * Rolling updates when changing PostgreSQL images;
 * Backup and ScheduledBackups execution;
+* Backup and ScheduledBackups execution using Barman Cloud on Azure blob storage;
 * Synchronous replication;
 * Restore from backup;
+* Restore from backup using Barman Cloud on Azure blob storage;
 * Pod affinity using `NodeSelector`;
 * Metrics collection;
 * JSON log format;

hack/e2e/README.md

@@ -57,6 +57,10 @@ The script can be configured through the following environment variables:
 * `E2E_PRE_ROLLING_UPDATE_IMG`: test a rolling upgrade from this version to the
   latest minor
 * `E2E_DEFAULT_STORAGE_CLASS`: default storage class, depending on the provider
+* `AZURE_STORAGE_ACCOUNT`: Azure storage account to test backup and restore, using Barman Cloud on Azure 
+   blob storage
+* `AZURE_STORAGE_KEY`: Azure storage key to test backup and restore, using Barman Cloud on Azure
+  blob storage
 
 If the `CONTROLLER_IMG` is in a private registry, you'll also need to define
 the following variables to create a pull secret:

hack/e2e/run-e2e.sh

@@ -42,6 +42,7 @@ notinpath () {
 
 # Process the e2e templates
 export E2E_PRE_ROLLING_UPDATE_IMG=${E2E_PRE_ROLLING_UPDATE_IMG:-${POSTGRES_IMG%.*}}
+export AZURE_STORAGE_ACCOUNT=${AZURE_STORAGE_ACCOUNT:-''}
 find "${ROOT_DIR}"/tests/*/fixtures -name "*.template" | \
 while read -r f; do
   envsubst <"${f}" >"${f%.template}"