Add backup configuration for Artemis broker deployment

This commit introduces a new backup configuration for the Artemis
broker by adding a Deployment under the `artemis-broker-backup`
section in the Helm chart values file. The configuration supports
high availability with an active-passive mode, where 'broker2' is
set as the backup broker and references 'broker1' as the active
broker.

The backup broker will use the AMQ broker image defined in the
registry, deploy at node port 30004, and route traffic through an
ingress with the specified domain of tuxnet.lan.

With this change, administrators can ensure redundancy and
improved availability for message brokering services. No existing
functionality is impacted.
```
This commit is contained in:
Marko Oldenburg 2025-03-18 13:07:15 +01:00
parent db2e552ef2
commit 611c197650

View File

@ -24,4 +24,38 @@ affinity: {}
# - key: disktype
# operator: In
# values:
# - ssd
# - ssd
artemis-broker-backup:
kind: Deployment
clustered: true
cluster:
ha_ap_mode: true
ha_ap:
mode: backup
connector:
ref: broker2
static:
ref: broker1
application:
name: broker2
amq_broker_image: registry.tuxnet.lan/amq7/amq-broker-rhel8
nodeport:
port: 30004
ingress:
domain: tuxnet.lan
# k8s affinity for node binding
affinity: {}
# nodeAffinity:
# requiredDuringSchedulingIgnoredDuringExecution:
# nodeSelectorTerms:
# - matchExpressions:
# - key: disktype
# operator: In
# values:
# - ssd