helm-controller VS helm-operator

If you're using helm I believe the helm controller could help you here

I agree with Helm Operator, though it is in maintenance mode and on the cusp of replacement with a newer tool. I'm working with FluxCD org now, on the next generation of Helm Operator, check out Helm Controller, under the new Flux2 which is rapidly approaching 100% feature parity (in the sense of approaching a limit, it is for almost all use cases 100% feature parity already) with the stable Flux v1 + Helm Operator.

You can store the values file of the helm in your repository and deploy with CI, but I personally prefer going to GitOps and Helm Operator (https://github.com/fluxcd/helm-operator) Or you can have a mixed approach where you define your HelmRelease to be deployed for HelmOperator and deploy it with CI (instead of having an operator in the cluster to apply every change in the repo)

Nothing prevents you from making an operator that creates Deployment/Services/Ingress for you.

This is even simplified with Helm (to template your resources) and the HelmOperator[1].

[1] - https://github.com/fluxcd/helm-operator

I think you should check out flux and flux helm operator. https://github.com/fluxcd/helm-operator/stargazers

fluxcd/helm-operator (Go): The Flux Helm Operator, for declarative Helming