Barman Cloud Integration Plugin Fails
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- go, kubernetes, postgresql
- Domain
- backend, databases, infrastructure
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.
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?
- Dominant language
- Go
- Stars
- 192
- Forks
- 75
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 17
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudnative-pg/plugin-barman-cloud
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
cloudnative-pg/plugin-barman-cloud#1104 · 4 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
cloudnative-pg/plugin-barman-cloud#1113 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 15/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in cloudnative-pg/plugin-barman-cloud
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Bob Shell support Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
santhosh-tekuri/jsonschema#276 ·