Use static clientID prefix in mqtt-pulsar-forwarder (also in k8s config) AND make sure replicas run in different AZs

tvv-lippu-ja-maksujarjestelma-oy / waltti-apc

The APC system for Waltti

European Union Public License 1.2

5 stars 1 forks source link

Use static clientID prefix in mqtt-pulsar-forwarder (also in k8s config) AND make sure replicas run in different AZs #206

Closed haphut closed 11 months ago

haphut commented 1 year ago

mqtt-pulsar-forwarder currently separates client ID of the replicas by randomizing the suffix within the instance, similar to e.g. pulsar-forwarder-jRnvjs4. Instead, use a static client ID, e.g. pulsar-forwarder-1-<SECRET> for MQTT protocol v3.1.1 (<SECRET> due to protocol DoS bug) or maybe just pulsar-forwarder-1 for MQTT protocol v5 (need to check).

But how to succinctly configure Kubernetes to run otherwise identical replicas in separate AZs using different secrets or configmaps?

haphut commented 11 months ago

Not necessary as we have three replicas in different AZs. when one replica drops and loses some data, we have the other two replicas to cover for it.