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.
This commit is contained in:
parent
ef7e4fb7d1
commit
b96a568c4d
8 changed files with 68 additions and 0 deletions
7
apps/rabbitmq-operators/base/kustomization.yaml
Normal file
7
apps/rabbitmq-operators/base/kustomization.yaml
Normal file
|
|
@ -0,0 +1,7 @@
|
|||
apiVersion: kustomize.config.k8s.io/v1beta1
|
||||
kind: Kustomization
|
||||
namespace: rabbitmq-system
|
||||
resources:
|
||||
- ../upstream/cluster-operator
|
||||
- ../upstream/message-topology-operator
|
||||
- namespace.yaml
|
||||
8
apps/rabbitmq-operators/base/namespace.yaml
Normal file
8
apps/rabbitmq-operators/base/namespace.yaml
Normal file
|
|
@ -0,0 +1,8 @@
|
|||
apiVersion: v1
|
||||
kind: Namespace
|
||||
metadata:
|
||||
labels:
|
||||
app.kubernetes.io/component: rabbitmq-operator
|
||||
app.kubernetes.io/name: rabbitmq-system
|
||||
app.kubernetes.io/part-of: rabbitmq
|
||||
name: rabbitmq-system
|
||||
11
apps/rabbitmq-operators/overlays/work/config.json
Normal file
11
apps/rabbitmq-operators/overlays/work/config.json
Normal file
|
|
@ -0,0 +1,11 @@
|
|||
{
|
||||
"appName": "rabbitmq-cluster",
|
||||
"userGivenName": "rabbitmq-cluster",
|
||||
"destNamespace": "rabbitmq-system",
|
||||
"destServer": "https://kubernetes.default.svc",
|
||||
"srcPath": "apps/rabbitmq-cluster/overlays/work",
|
||||
"srcRepoURL": "ssh://git@gitea-ssh.gitops.svc.cluster.local:2222/davad/argo.git",
|
||||
"srcTargetRevision": "",
|
||||
"labels": null,
|
||||
"annotations": null
|
||||
}
|
||||
4
apps/rabbitmq-operators/overlays/work/kustomization.yaml
Normal file
4
apps/rabbitmq-operators/overlays/work/kustomization.yaml
Normal file
|
|
@ -0,0 +1,4 @@
|
|||
apiVersion: kustomize.config.k8s.io/v1beta1
|
||||
kind: Kustomization
|
||||
resources:
|
||||
- ../../base
|
||||
|
|
@ -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
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
$patch: delete
|
||||
apiVersion: v1
|
||||
kind: Namespace
|
||||
metadata:
|
||||
name: rabbitmq-system
|
||||
|
|
@ -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
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
$patch: delete
|
||||
apiVersion: v1
|
||||
kind: Namespace
|
||||
metadata:
|
||||
name: rabbitmq-system
|
||||
Loading…
Add table
Add a link
Reference in a new issue