@allan
I see it as part of the learning / maturity progression path for both individuals and companies making their way through adopting container based application ecosystems.

"What's a #container? Oh, cool!"
"Wait, I can string a few together to make an app? This #DockerCompose thing looks neat."
"So you're telling me there's this #Kubernetes thing that allows me to scale this?"
"Oh good, #Helm is a way I can pack all these bits together for my app and deploy them at once."
"What do you mean I can store all of this into git and not have to deploy manually? I'll have to take a look at this #gitops concept."

It can take people and companies a while to go through all of these stages.

There are likely more stages, but this is the progress path I have experienced so far. I'll still use the Helm CLI for testing and making sure my templates build before I commit changes back to the repo.

I can also see where Helm CLI would remain useful even in a company that follows gitops, for example a deployment to a Kubernetes cluster that can't talk to your gitops platform for whatever reason.