cloudnative-pg / cloudnative-pg/plugin-barman-cloud
Barman Cloud Integration Plugin Fails
- Dominant language
- Go
- Stars
- 192
- Forks
- 75
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 18
Description
plugins:
name: barman-cloud.cloudnative-pg.io
isWALArchiver: true
parameters:
barmanObjectName: minio-store
When we apply the Plugin we get the following error:
{"level":"error","ts":"2026-02-10T01:27:20.782025709Z","msg":"Reconciler error","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"licloud-pg-cluster","namespace":"cnpg-system"},"namespace":"cnpg-system","name":"licloud-pg-cluster","reconcileID":"e5fe6d86-f9d8-4e81-870c-b1e36b600fdb","error":"unable to create Pod: Pod "licloud-pg-cluster-3" is invalid: spec.initContainers[1].startupProbe: Forbidden: may not be set for init containers","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler\n\tpkg/mod/sigs.k8s.io/controller-runtime@v0.22.4/pkg/internal/controller/controller.go:474\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem\n\tpkg/mod/sigs.k8s.io/controller-runtime@v0.22.4/pkg/internal/controller/controller.go:421\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func1.1\n\tpkg/mod/sigs.k8s.io/controller-runtime@v0.22.4/pkg/internal/controller/controller.go:296"}
We are on:
- Kuberenetes Version v1.30.14
- Barman Plugin Version v0.11.0
- Cloud Native PG Version v1.28.1
All Resources (ServiceAccounts, ObjectStore, Cluster, Operator, etc.) are installed in the same namespace.
We are not using Istio.
Ist there any timeline on when this bug will be fixed?
Contributor guide
Research direction
Start by reproducing the Plugin configuration on Kubernetes v1.30.14 with Barman Plugin v0.11.0 and Cloud Native PG v1.28.1. Inspect the generated Pod, especially initContainers[1], to find why startupProbe is being set on an init container. Done means the Cluster creates its Pod without the validation error and the Barman Cloud integration remains functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- backend, databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100