redpanda-data / redpanda-data/redpanda-operator
Allow console clusterRef to reverence cluster in different namespace
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 84
- Forks
- 32
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 104
Description
I want to deploy the console and the redpanda cluster in two different namespaces. Mainly to have the config separated and for easier network rule and policy configuration.
Could you add an optional namespace field to clusterRef to reference a cluster in a different namespace? For example:
apiVersion: cluster.redpanda.com/v1alpha2
kind: Console
metadata:
name: console
spec:
cluster:
clusterRef:
name: redpanda
namespace: redpanda-cluster
In the code it looks like it always sets the namespace to the namespace of the console resource.
Not sure if there are security concerns or if the clusterRef mechanism would work if not in the same namespace.
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 Console clusterRef handling described in the issue and trace where the namespace is assigned from the Console resource. Check how the operator resolves a Redpanda cluster reference across namespaces and review the security implications. Done means the example namespace is honored without breaking same-namespace references, with validation or tests for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100