Lots of Pipelines during release procedure
The release procedure does a few things which cause a lot of pipelines to kick off, some of these may not be necessary. In the example below, we released version 4.1.0 of the helm chart. This release causes some version bumps, stable and master branch updates, a tag, all of which end up with their own unique pipeline:
See if we can trim the amount of jobs running to reduce CI run time.