Congrats! I could see the value of this, for sure. I handle this problem by spinning up a preview environment in a namespace. Each branch gets its own and a script takes care of setting up namespaces for a couple of shared resources for staging (rabbit and temporal).
It was a lot of work setting that up though. Preview environments based on a helm deploy makes sense. I wish this had been available before I did all that.
Thanks for the feedback — you’re spot on about the setup this is trying to speed up. The namespace-per-branch approach works well (and that’s what this does), but the setup around ingress, DNS, secrets, and cleanup tends to be the real time sink. Glad it resonates.
Thanks again.