Separate monitoring node

SolaceProducts / pubsubplus-kubernetes-helm-quickstart

Quickstart to launch a Solace PubSub+ Software Event Broker in Kubernetes using Helm

Apache License 2.0

32 stars 44 forks source link

Separate monitoring node #104

Closed pjgunadi closed 1 year ago

pjgunadi commented 3 years ago

Consider to separate monitoring node, considering it requires smaller cpu, memory, and disk. I tried on my fork:

created a copy of solaceStatefulSet to monitorStatefulSet and gave a name suffix '-m'
modified configmap using name suffix for monitoring node / redundancy mates identification replacing/in addition to the statefulsets ordinal number
added monsize in values.yaml for monitoring disk size

bczoma commented 3 years ago

@pjgunadi - Hi Paulus, thanks for the contribution! Looking at the code changes this seems to work. You'd want to ensure that as long as there are more than 2 availability zones the monitor is always in a different AZ than the other two PubSub+ broker nodes. One way to do it is by using affinity/taints to designate K8s nodes for monitor use. We have planned work to update the broker Helm chart to enable smaller monitor size and what you just did is certainly one of the options.

bczoma commented 1 year ago

Closing this PR as support for small Monitor has been implemented differently