cloudnative-pg / cloudnative-pg/plugin-barman-cloud
[feature request] Allow specifying namespace of Barman ObjectStore CR
- Lenguaje dominante
- Go
- Estrellas
- 191
- Forks
- 72
- Merge medio
- 2 d 21 h
- PR fusionados (30 d)
- 21
Descripción
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.:
```yaml
---
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:
endpointURL:
s3Credentials:
# Configure namespace access
allowAccessFromNamespace: true
# Maybe allow explicitly specifying the namespace(s):
allowAccessFromNamespaces:
- cluster-namespace
```
Guía de contribución
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- go, kubernetes, postgresql
- Área
- backend-api-design, databases
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 25/100