Merge e809896f45 into dd541aae44

This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| gh | digest | `5dcc7e4` → `5f2dc1b` |
| golangci-lint | digest | `5dcc7e4` → `5f2dc1b` |
| kustomize | digest | `5dcc7e4` → `5f2dc1b` |

---

> [!WARNING]
> Some dependencies could not be looked up. Check the [Dependency
Dashboard](../issues/7) for more information.

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - At any time (no schedule defined)
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Never, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about these
updates again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/cloudnative-pg/plugin-barman-cloud).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xNTkuMiIsInVwZGF0ZWRJblZlciI6IjQzLjE1OS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJhdXRvbWF0ZWQiLCJuby1pc3N1ZSJdfQ==-->

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Taskfile.yml

@@ -21,7 +21,7 @@ tasks:
     desc: Run golangci-lint
     env:
       # renovate: datasource=git-refs depName=golangci-lint lookupName=https://github.com/sagikazarmark/daggerverse currentValue=main
-      DAGGER_GOLANGCI_LINT_SHA: 5dcc7e4c4cd5ed230046955f42e27f2166545155
+      DAGGER_GOLANGCI_LINT_SHA: 5f2dc1bd1014cf79757f4605f2f731ed962d4da7
       # renovate: datasource=docker depName=golangci/golangci-lint versioning=semver
       GOLANGCI_LINT_VERSION: v2.11.4
     cmds:
@@ -133,7 +133,7 @@ tasks:
       # renovate: datasource=git-refs depname=kubernetes packageName=https://github.com/kubernetes/kubernetes versioning=semver
       K8S_VERSION: 1.31.0
       # renovate: datasource=git-refs depName=controller-runtime packageName=https://github.com/kubernetes-sigs/controller-runtime versioning=semver
-      SETUP_ENVTEST_VERSION: 0.23.3
+      SETUP_ENVTEST_VERSION: 0.24.0
     cmds:
       - >
         GITHUB_REF= dagger -s call -m ./dagger/gotest
@@ -453,7 +453,7 @@ tasks:
       IMAGE_VERSION: '{{regexReplaceAll "(\\d+)/merge" .GITHUB_REF_NAME "pr-${1}"}}'
     env:
       # renovate: datasource=git-refs depName=kustomize lookupName=https://github.com/sagikazarmark/daggerverse currentValue=main
-      DAGGER_KUSTOMIZE_SHA: 5dcc7e4c4cd5ed230046955f42e27f2166545155
+      DAGGER_KUSTOMIZE_SHA: 5f2dc1bd1014cf79757f4605f2f731ed962d4da7
     cmds:
       - >
         dagger -s call -m https://github.com/sagikazarmark/daggerverse/kustomize@${DAGGER_KUSTOMIZE_SHA}
@@ -483,7 +483,7 @@ tasks:
         - GITHUB_TOKEN
     env:
       # renovate: datasource=git-refs depName=gh lookupName=https://github.com/sagikazarmark/daggerverse
-      DAGGER_GH_SHA: 5dcc7e4c4cd5ed230046955f42e27f2166545155
+      DAGGER_GH_SHA: 5f2dc1bd1014cf79757f4605f2f731ed962d4da7
     preconditions:
       - sh: "[[ {{.GITHUB_REF}} =~ 'refs/tags/v.*' ]]"
         msg: not a tag, failing

web/docs/installation.mdx

@@ -56,6 +56,8 @@ Both checks are required before proceeding with the installation.
 
 import { InstallationSnippet } from '@site/src/components/Installation';
 
+### Directly using the manifest
+
 Install the plugin using `kubectl` by applying the manifest for the latest
 release:
 
@@ -98,6 +100,18 @@ deployment "barman-cloud" successfully rolled out
 
 This confirms that the plugin is deployed and ready to use.
 
+### Using the Helm Chart
+
+The plugin can be installed using the provided [Helm chart](https://github.com/cloudnative-pg/charts/tree/main/charts/plugin-barman-cloud):
+
+```sh
+helm repo add cnpg https://cloudnative-pg.github.io/charts
+helm upgrade --install barman-cloud \
+  --namespace cnpg-system \
+  --create-namespace \
+  cnpg/plugin-barman-cloud
+```
+
 ## Testing the latest development snapshot
 
 You can also test the latest development snapshot of the plugin with the

web/docs/troubleshooting.md

@@ -485,14 +485,10 @@ If problems persist:
 
 ### Plugin Limitations
 
-1. **Installation method**: Currently only supports manifest and Kustomize
+1. **Sidecar resource sharing**: The plugin sidecar container shares pod
-   installation ([#351](https://github.com/cloudnative-pg/plugin-barman-cloud/issues/351) -
-   Helm chart requested)
-
-2. **Sidecar resource sharing**: The plugin sidecar container shares pod
    resources with PostgreSQL
 
-3. **Plugin restart behavior**: Restarting the sidecar container requires
+2. **Plugin restart behavior**: Restarting the sidecar container requires
    restarting the entire PostgreSQL pod
 
 ## Recap of General Debugging Steps
@@ -588,4 +584,3 @@ kubectl get secret -n <namespace> <secret-name> -o jsonpath='{.data}' | jq 'keys
 * **"NoSuchBucket"** — Verify the bucket exists and the endpoint URL is correct.
 * **"Connection timeout"** — Check network connectivity and firewall rules.
 * **"SSL certificate problem"** — For self-signed certificates, verify the CA bundle configuration.
-

web/versioned_docs/version-0.10.0/installation.mdx

@@ -56,6 +56,8 @@ Both checks are required before proceeding with the installation.
 
 import { InstallationSnippet } from '@site/src/components/Installation';
 
+### Directly using the manifest
+
 Install the plugin using `kubectl` by applying the manifest for the latest
 release:
 
@@ -98,6 +100,19 @@ deployment "barman-cloud" successfully rolled out
 
 This confirms that the plugin is deployed and ready to use.
 
+### Using the Helm Chart
+
+The plugin can be installed using the provided [Helm chart](https://github.com/cloudnative-pg/charts/tree/main/charts/plugin-barman-cloud):
+
+```sh
+helm repo add cnpg https://cloudnative-pg.github.io/charts
+helm upgrade --install barman-cloud \
+  --namespace cnpg-system \
+  --create-namespace \
+  --version 0.4.0 \
+  cnpg/plugin-barman-cloud
+```
+
 ## Testing the latest development snapshot
 
 You can also test the latest development snapshot of the plugin with the

web/versioned_docs/version-0.10.0/troubleshooting.md

@@ -485,14 +485,10 @@ If problems persist:
 
 ### Plugin Limitations
 
-1. **Installation method**: Currently only supports manifest and Kustomize
+1. **Sidecar resource sharing**: The plugin sidecar container shares pod
-   installation ([#351](https://github.com/cloudnative-pg/plugin-barman-cloud/issues/351) -
-   Helm chart requested)
-
-2. **Sidecar resource sharing**: The plugin sidecar container shares pod
    resources with PostgreSQL
 
-3. **Plugin restart behavior**: Restarting the sidecar container requires
+2. **Plugin restart behavior**: Restarting the sidecar container requires
    restarting the entire PostgreSQL pod
 
 ## Recap of General Debugging Steps
@@ -588,4 +584,3 @@ kubectl get secret -n <namespace> <secret-name> -o jsonpath='{.data}' | jq 'keys
 * **"NoSuchBucket"** — Verify the bucket exists and the endpoint URL is correct.
 * **"Connection timeout"** — Check network connectivity and firewall rules.
 * **"SSL certificate problem"** — For self-signed certificates, verify the CA bundle configuration.
-

web/versioned_docs/version-0.11.0/installation.mdx

@@ -56,6 +56,8 @@ Both checks are required before proceeding with the installation.
 
 import { InstallationSnippet } from '@site/src/components/Installation';
 
+### Directly using the manifest
+
 Install the plugin using `kubectl` by applying the manifest for the latest
 release:
 
@@ -98,6 +100,19 @@ deployment "barman-cloud" successfully rolled out
 
 This confirms that the plugin is deployed and ready to use.
 
+### Using the Helm Chart
+
+The plugin can be installed using the provided [Helm chart](https://github.com/cloudnative-pg/charts/tree/main/charts/plugin-barman-cloud):
+
+```sh
+helm repo add cnpg https://cloudnative-pg.github.io/charts
+helm upgrade --install barman-cloud \
+  --namespace cnpg-system \
+  --create-namespace \
+  --version 0.5.0 \
+  cnpg/plugin-barman-cloud
+```
+
 ## Testing the latest development snapshot
 
 You can also test the latest development snapshot of the plugin with the

web/versioned_docs/version-0.11.0/troubleshooting.md

@@ -485,14 +485,10 @@ If problems persist:
 
 ### Plugin Limitations
 
-1. **Installation method**: Currently only supports manifest and Kustomize
+1. **Sidecar resource sharing**: The plugin sidecar container shares pod
-   installation ([#351](https://github.com/cloudnative-pg/plugin-barman-cloud/issues/351) -
-   Helm chart requested)
-
-2. **Sidecar resource sharing**: The plugin sidecar container shares pod
    resources with PostgreSQL
 
-3. **Plugin restart behavior**: Restarting the sidecar container requires
+2. **Plugin restart behavior**: Restarting the sidecar container requires
    restarting the entire PostgreSQL pod
 
 ## Recap of General Debugging Steps
@@ -588,4 +584,3 @@ kubectl get secret -n <namespace> <secret-name> -o jsonpath='{.data}' | jq 'keys
 * **"NoSuchBucket"** — Verify the bucket exists and the endpoint URL is correct.
 * **"Connection timeout"** — Check network connectivity and firewall rules.
 * **"SSL certificate problem"** — For self-signed certificates, verify the CA bundle configuration.
-

web/versioned_docs/version-0.12.0/installation.mdx

@@ -56,6 +56,8 @@ Both checks are required before proceeding with the installation.
 
 import { InstallationSnippet } from '@site/src/components/Installation';
 
+### Directly using the manifest
+
 Install the plugin using `kubectl` by applying the manifest for the latest
 release:
 
@@ -98,6 +100,19 @@ deployment "barman-cloud" successfully rolled out
 
 This confirms that the plugin is deployed and ready to use.
 
+### Using the Helm Chart
+
+The plugin can be installed using the provided [Helm chart](https://github.com/cloudnative-pg/charts/tree/main/charts/plugin-barman-cloud):
+
+```sh
+helm repo add cnpg https://cloudnative-pg.github.io/charts
+helm upgrade --install barman-cloud \
+  --namespace cnpg-system \
+  --create-namespace \
+  --version 0.6.0 \
+  cnpg/plugin-barman-cloud
+```
+
 ## Testing the latest development snapshot
 
 You can also test the latest development snapshot of the plugin with the

web/versioned_docs/version-0.12.0/troubleshooting.md

@@ -485,14 +485,10 @@ If problems persist:
 
 ### Plugin Limitations
 
-1. **Installation method**: Currently only supports manifest and Kustomize
+1. **Sidecar resource sharing**: The plugin sidecar container shares pod
-   installation ([#351](https://github.com/cloudnative-pg/plugin-barman-cloud/issues/351) -
-   Helm chart requested)
-
-2. **Sidecar resource sharing**: The plugin sidecar container shares pod
    resources with PostgreSQL
 
-3. **Plugin restart behavior**: Restarting the sidecar container requires
+2. **Plugin restart behavior**: Restarting the sidecar container requires
    restarting the entire PostgreSQL pod
 
 ## Recap of General Debugging Steps
@@ -588,4 +584,3 @@ kubectl get secret -n <namespace> <secret-name> -o jsonpath='{.data}' | jq 'keys
 * **"NoSuchBucket"** — Verify the bucket exists and the endpoint URL is correct.
 * **"Connection timeout"** — Check network connectivity and firewall rules.
 * **"SSL certificate problem"** — For self-signed certificates, verify the CA bundle configuration.
-

web/versioned_docs/version-0.5.0/installation.mdx

@@ -56,6 +56,8 @@ Both checks are required before proceeding with the installation.
 
 import { InstallationSnippet } from '@site/src/components/Installation';
 
+### Directly using the manifest
+
 Install the plugin using `kubectl` by applying the manifest for the latest
 release:
 
@@ -98,6 +100,19 @@ deployment "barman-cloud" successfully rolled out
 
 This confirms that the plugin is deployed and ready to use.
 
+### Using the Helm Chart
+
+The plugin can be installed using the provided [Helm chart](https://github.com/cloudnative-pg/charts/tree/main/charts/plugin-barman-cloud):
+
+```sh
+helm repo add cnpg https://cloudnative-pg.github.io/charts
+helm upgrade --install barman-cloud \
+  --namespace cnpg-system \
+  --create-namespace \
+  --version 0.1.0 \
+  cnpg/plugin-barman-cloud
+```
+
 ## Testing the latest development snapshot
 
 You can also test the latest development snapshot of the plugin with the

web/versioned_docs/version-0.7.0/installation.mdx

@@ -56,6 +56,8 @@ Both checks are required before proceeding with the installation.
 
 import { InstallationSnippet } from '@site/src/components/Installation';
 
+### Directly using the manifest
+
 Install the plugin using `kubectl` by applying the manifest for the latest
 release:
 
@@ -98,6 +100,19 @@ deployment "barman-cloud" successfully rolled out
 
 This confirms that the plugin is deployed and ready to use.
 
+### Using the Helm Chart
+
+The plugin can be installed using the provided [Helm chart](https://github.com/cloudnative-pg/charts/tree/main/charts/plugin-barman-cloud):
+
+```sh
+helm repo add cnpg https://cloudnative-pg.github.io/charts
+helm upgrade --install barman-cloud \
+  --namespace cnpg-system \
+  --create-namespace \
+  --version 0.2.0 \
+  cnpg/plugin-barman-cloud
+```
+
 ## Testing the latest development snapshot
 
 You can also test the latest development snapshot of the plugin with the

web/versioned_docs/version-0.7.0/troubleshooting.md

@@ -474,14 +474,10 @@ If problems persist:
 
 ### Plugin Limitations
 
-1. **Installation method**: Currently only supports manifest and Kustomize
+1. **Sidecar resource sharing**: The plugin sidecar container shares pod
-   installation ([#351](https://github.com/cloudnative-pg/plugin-barman-cloud/issues/351) -
-   Helm chart requested)
-
-2. **Sidecar resource sharing**: The plugin sidecar container shares pod
    resources with PostgreSQL
 
-3. **Plugin restart behavior**: Restarting the sidecar container requires
+2. **Plugin restart behavior**: Restarting the sidecar container requires
    restarting the entire PostgreSQL pod
 
 ## Recap of General Debugging Steps
@@ -577,4 +573,3 @@ kubectl get secret -n <namespace> <secret-name> -o jsonpath='{.data}' | jq 'keys
 * **"NoSuchBucket"** — Verify the bucket exists and the endpoint URL is correct.
 * **"Connection timeout"** — Check network connectivity and firewall rules.
 * **"SSL certificate problem"** — For self-signed certificates, verify the CA bundle configuration.
-

web/versioned_docs/version-0.9.0/installation.mdx

@@ -56,6 +56,8 @@ Both checks are required before proceeding with the installation.
 
 import { InstallationSnippet } from '@site/src/components/Installation';
 
+### Directly using the manifest
+
 Install the plugin using `kubectl` by applying the manifest for the latest
 release:
 
@@ -98,6 +100,19 @@ deployment "barman-cloud" successfully rolled out
 
 This confirms that the plugin is deployed and ready to use.
 
+### Using the Helm Chart
+
+The plugin can be installed using the provided [Helm chart](https://github.com/cloudnative-pg/charts/tree/main/charts/plugin-barman-cloud):
+
+```sh
+helm repo add cnpg https://cloudnative-pg.github.io/charts
+helm upgrade --install barman-cloud \
+  --namespace cnpg-system \
+  --create-namespace \
+  --version 0.3.1 \
+  cnpg/plugin-barman-cloud
+```
+
 ## Testing the latest development snapshot
 
 You can also test the latest development snapshot of the plugin with the

web/versioned_docs/version-0.9.0/troubleshooting.md

@@ -474,14 +474,10 @@ If problems persist:
 
 ### Plugin Limitations
 
-1. **Installation method**: Currently only supports manifest and Kustomize
+1. **Sidecar resource sharing**: The plugin sidecar container shares pod
-   installation ([#351](https://github.com/cloudnative-pg/plugin-barman-cloud/issues/351) -
-   Helm chart requested)
-
-2. **Sidecar resource sharing**: The plugin sidecar container shares pod
    resources with PostgreSQL
 
-3. **Plugin restart behavior**: Restarting the sidecar container requires
+2. **Plugin restart behavior**: Restarting the sidecar container requires
    restarting the entire PostgreSQL pod
 
 ## Recap of General Debugging Steps
@@ -577,4 +573,3 @@ kubectl get secret -n <namespace> <secret-name> -o jsonpath='{.data}' | jq 'keys
 * **"NoSuchBucket"** — Verify the bucket exists and the endpoint URL is correct.
 * **"Connection timeout"** — Check network connectivity and firewall rules.
 * **"SSL certificate problem"** — For self-signed certificates, verify the CA bundle configuration.
-