zalando / zalando/postgres-operator
Not managed credential is getting deleted by operator along with postgresql resource
Nobody has claimed this yet.
- 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? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.8.2
Where do you run it - cloud or metal? Kubernetes or OpenShift? [Bare Metal K8s]
Are you running Postgres Operator in production? [not yet]
Type of issue? [feature requrest]
So to have managed creds I have to create them beforehand as a secret with Zalando specific name, and then if I delete the postgresql resource, operator deletes this credential as well, which is unwanted. Could you make operator label somehow resource with additional label and only then delete the cred?
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
No files, tests, or entry points are named in the issue. Start by tracing how the operator identifies and deletes managed credential Secrets when a PostgreSQL resource is removed, then inspect existing resource labels and deletion tests. Done means externally created credentials are retained while operator-owned credentials are still deleted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100