zalando / zalando/postgres-operator

UI does not allow selecting namespace for a new cluster and clusters from other namespaces are not displayed

Open
#3,157 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
5.2k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
3

Description

Description

I found two related issues in the Postgres Operator UI.

1. Cannot choose a namespace when creating a cluster

The "Create Cluster" form does not provide any option to select the target Kubernetes namespace. As a result, the generated manifest is created only for the default namespace used by the UI.

2. Clusters created in another namespace are not visible

As a workaround, I generated the manifest in the UI and manually changed the metadata.namespace before applying it.

The PostgreSQL cluster was successfully created and is fully operational in the target namespace. However, it does not appear in the UI's cluster list.

Expected behavior
  • The UI should allow selecting the target namespace when creating a new PostgreSQL cluster.
  • The cluster list should display clusters from all namespaces that the UI has permission to access, or at least provide a namespace selector/filter.
Actual behavior
  • There is no namespace selector during cluster creation.
  • Clusters deployed outside the default namespace are not shown in the UI, even though they exist and are managed by the operator.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Create Cluster form and the cluster-list entry point, tracing how the manifest namespace is chosen and which namespaces are queried for display. Done means users can select a target namespace when creating a cluster and can see accessible clusters from other namespaces, with a namespace filter if needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes, postgresql
Domain
database, devops, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.