You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have AWS Managed RabbitMQ and I want to allow my k8s cluster tenants create RabbitMQ objects using Topology Operator.
To manage external RabbitMQ I have to specify spec.rabbitmqClusterReference.connectionSecret.name in a RMQ Custom Resource. By default, the Custom Resources allowed only from the Topology Operator namespace. But, I want to allow tenants to create RMQ CustomResources in their own namespaces. In normal way I can annotate RabbitmqCluster CR with rabbitmq.com/topology-allowed-namespaces. But in my case I don't have the RabbitmqCluster CR.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, thanks for the operators.
I have AWS Managed RabbitMQ and I want to allow my k8s cluster tenants create RabbitMQ objects using Topology Operator.
To manage external RabbitMQ I have to specify
spec.rabbitmqClusterReference.connectionSecret.name
in a RMQ Custom Resource. By default, the Custom Resources allowed only from the Topology Operator namespace. But, I want to allow tenants to create RMQ CustomResources in their own namespaces. In normal way I can annotateRabbitmqCluster
CR withrabbitmq.com/topology-allowed-namespaces
. But in my case I don't have theRabbitmqCluster
CR.Beta Was this translation helpful? Give feedback.
All reactions