Skip to content

Allow console clusterRef to reverence cluster in different namespace #1198

@yvespp

Description

@yvespp

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions