zalando / zalando/postgres-operator
Running the operator in namespace scoped mode
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?
registry.opensource.zalan.do/acid/postgres-operator:v1.8.2-17-gb48034d7-dev - Where do you run it - cloud or metal? Kubernetes or OpenShift?
minikube, using run_operator_locally.sh - Are you running Postgres Operator in production? [yes | no]
no - Type of issue? [Bug report, question, feature request, etc.]
Question
Is there a way to run this operator in a single namespace mode so that it does not require cluster-wide permissions? I am aware of the watched_namespace setting. I tried setting that to a namespace that I created and ran the operator using the script as described above. But it still created a bunch of clusterrole and clusterrolebindings. I am looking for a k8s manifest that sets up the operator only with namespace scoped role and rolebindings.
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 inspecting run_operator_locally.sh and the watched_namespace setting described in the issue. Determine how the local-run manifests create cluster-wide RBAC, then identify the manifest configuration needed for a single namespace. Done means the operator runs with namespace-scoped Roles and RoleBindings without requiring ClusterRoles or ClusterRoleBindings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100