We're using helm, but that was chosen mostly based on gut feel. It's an official project, and has momentum. We didn't want to spend too much time choosing a tool until we knew our requirements, and we don't really have a firm grasp of requirements until we've used something for a while. It seems to be working well for us so far, but it's still early.
There are lots of answers here that aren't helm, so I'm curious if there are any particular reasons that people ruled out helm?
We ran into a number of issues with Helm when deploying - failures leading us to have to rollback, with rollbacks then failing, requiring manual changes to unblock.
I think that for third-party packages and related templating (which seems like the original use-case) it works well, but I would be wary of using it for high-res deploys of our own stuff.
Are you doing what Gitlab claims below "We (GitLab) use it mostly as a templating system as well" or really using it to manage complex apps? I think it doesn't really offer much for normal microservices.
I do use it for things like nginx ingress but for stuff I've built a service.yml / deployment.yml are fine.
There are lots of answers here that aren't helm, so I'm curious if there are any particular reasons that people ruled out helm?