chore(work): testing rabbitmq operator deployment

RabbitMQ has two operators. Their docs claim you have to install the first,
spin up a cluster, _then_ add the other operator. I'm testing installing both
operators at once.

apps/rabbitmq-operators/upstream/cluster-operator/kustomization.yaml

@@ -0,0 +1,14 @@
+# Both upstream operators define the namespace 'rabbitmq-system'. We need to
+# remove one of those resources to avoid problems.
+apiVersion: kustomize.config.k8s.io/v1beta1
+kind: Kustomization
+namespace: rabbitmq-system # This is the NS that the upstream manifest creates
+resources:
+  - https://github.com/rabbitmq/cluster-operator/config/installation?ref=v2.10.0
+
+images:
+  - name: rabbitmqoperator/cluster-operator
+    newTag: 2.10.0
+
+patches:
+  - path: ns.delete.yaml

apps/rabbitmq-operators/upstream/cluster-operator/ns.delete.yaml

@@ -0,0 +1,5 @@
+$patch: delete
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: rabbitmq-system

apps/rabbitmq-operators/upstream/message-topology-operator/kustomization.yaml

@@ -0,0 +1,14 @@
+# Both upstream operators define the namespace
+# 'rabbitmq-system'. To avoid issues, we're removing the
+# namespace from the upstream, then readding it downstream.
+apiVersion: kustomize.config.k8s.io/v1beta1
+kind: Kustomization
+resources:
+  - https://github.com/rabbitmq/messaging-topology-operator/config/installation/cert-manager?ref=v1.14.2
+
+images:
+  - name: rabbitmqoperator/messaging-topology-operator
+    newTag: 1.14.2
+
+patches:
+  - path: ns.delete.yaml

apps/rabbitmq-operators/upstream/message-topology-operator/ns.delete.yaml

@@ -0,0 +1,5 @@
+$patch: delete
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: rabbitmq-system