[feature request] Allow specifying namespace of Barman ObjectStore CR

Open

#741 opened on Jan 20, 2026 2 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 25/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Stale
Tech stack: go, kubernetes, postgresql
Domain: backend-api-design, databases

Research direction

Review the Cluster plugin parameters and ObjectStore custom-resource definitions to understand how the barmanObjectName is resolved today. Clarify the cross-namespace authorization model before implementation; done means a namespace can be specified safely, access can be restricted, and the behavior is covered by the relevant tests.

Written by the indexing model from the issue text.

Description

enhancement

Currently, the ObjectStore referenced in a Cluster has to be in the same namespace. It would be helpful to be able to specify a namespace where the ObjectStore should be fetched from.

This can have security implications and there should probably a mechanism to enable or disable the access from a different namespace. This could be a flag in the ObjectStore itself.

e.g.:

---
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name: test-cluster
  namespace: cluster-namespace
spec:
  instances: 3
  plugins:
    - name: barman-cloud.cloudnative-pg.io
      isWALArchiver: true
      parameters:
        barmanObjectName: s3-store
        barmanObjectNamespace: cnpg-system # Add the namespace here
---
apiVersion: barmancloud.cnpg.io/v1
kind: ObjectStore
metadata:
  name: s3-store
  namespace: cnpg-system
spec:
  configuration:
    destinationPath: <destination>
    endpointURL: <endpoint>
    s3Credentials: <s3Credentials>
    # Configure namespace access
    allowAccessFromNamespace: true
    # Maybe allow explicitly specifying the namespace(s):
    allowAccessFromNamespaces:
      - cluster-namespace

Dominant language: Go
Stars: 192
Forks: 75
Avg merge: 1d 7h
Merged PRs (30d): 17

Contributor guide

Open the contributing 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.

Similar issues

Smoke Test: Copilot - 35930762956 Open

Difficulty 1/5 Under an hour Newbie friendliness 60/100

github/gh-aw-mcpg#13748 · Opened Sep 23, 2026
[aw] Daily Reliability Review failed Open

agentic-workflows

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

github/gh-aw#63046 · Opened Sep 23, 2026
OpenVEX statements carry no subcomponent package or version Open

needs-triage

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

NVIDIA/aicr#2945 · Opened Sep 23, 2026
[Bug]: Event executions make the originating request panic (nil JobInsertResult in queue log middleware) when the OTLP log exporter is enabled Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

zitadel/zitadel#12811 · Opened Sep 23, 2026
java: Librarian prepends duplicate java- prefix when library name already includes it Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

googleapis/librarian#7670 · 2 comments · Opened Sep 23, 2026

More Go issues