Namespace collision with rabbitmq/cluster-operator #528
Replies: 1 comment 5 replies
-
Hi @Kamaradeivanov since version 1.4.0 the messaging topology operator can be deployed without requiring the cluster-operator ( https://www.rabbitmq.com/kubernetes/operator/using-topology-operator.html#non-operator). For this reason discussing with the team we decided that it is better not to remove the namespace definition in the messaging-operator definition file. In the long run there is a plan to merge the messaging operator into the cluster operator but it will not be something recent. In the meantime is there not any workaround for kustomize that we can implement for example using patchStrategicMerge or some other commands? For example here it seems like we have the same situation https://stackoverflow.com/questions/72288489/patching-multiple-resources-with-kustomize and was suggested to use components... I'm not a kustomize/argoCD expert but maybe in the community someone have some ideas/workaround we can implement. In any case I don't really think it can be considered as "bug" of the product. |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
Hello, first thing, thanks for the great job you have done with the both rabbitmq operator.
I'm currently using argocd to deploy rabbitmq in a gitops way. Recently i want to add Messaging Topology Kubernetes Operator to create vhost, policy and user with CRD.
To do that I try to used kustomize to easily deploy
rabbitmq/cluster-operator
andrabbitmq/messaging-topology-operator
but i'am currently facing a collision because the each operator deployment yaml start with :To Reproduce
To do that i' have the following kustomize file
Then I run
kustomize build .
And I got the following error
Expected behavior
In your (documentation)[https://github.com/rabbitmq/messaging-topology-operator/#quickstart] you says that :
If the RabbitMQ Cluster Operator must be installed why do you also create the nemaspace in the Messaging Topology Kubernetes Operator ?
Version and environment information
Beta Was this translation helpful? Give feedback.
All reactions