We explored how we can add Jenkins to the mix and make it scale any service. We used relative scaling and made sure that there are some limits so that the service will always be within some boundaries.
Jenkins, by itself, proved to be very flexible and allowed us to set up a reasonably bullet-proof scaling mechanism with only a few lines of Declarative Pipeline code. Unfortunately, we hit some limits when integrating Alertmanager with Jenkins. As a result, Alertmanager config is not as generic as we'd like it to be. We might revisit that subject later and apply some alternative strategy. We might want to extend it. The solution might be called Docker Flow Alertmanager. Or, we might choose to replace Jenkins with our own solution. Since I'm fond of names that start with Docker Flow, we might add Scaler to the mix. We might opt for something completely unexpected...
