zalando / zalando/postgres-operator
secretNamespace type
Open
Nobody has claimed this yet.
wontfix
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
- Which image of the operator are you using?
- registry.opensource.zalan.do/acid/postgres-operator:v1.8.1
- **Where do you run it ?
- Bare Metal K8s]
- Are you running Postgres Operator in production?
- No
- Type of issue?
- feature request
We deployed a PostgreSQL database in namespace A and we need the _owner _writer and _reader secrets in more than one another namespace.
Is it posible to change the secretNamespace type from string to array ??
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.
Research direction
Start by locating the operator configuration and schema for secretNamespace, then trace how the setting is used when creating _owner, _writer, and _reader secrets. Check any related validation or configuration tests; done means supporting multiple target namespaces without breaking the existing single-namespace behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100