Remove the namespace object or rename it `victoriametrics`

[stribb]

While it's convenient to create a namespace for the Victoriametrics operator, it has a massive downside in the case where the operator shares a namespace with other services.

In my setup, I (naturally) put Victoriametrics into the same NS as the operator, then went about adding several other services. This went fine until I had to delete Operator to re-create it. The most obvious way for me to delete it seemed that I should run kubectl delete -k kustomization.yaml. But, of course, since it also has the monitoring-system namespace, it deleted everything inside the namespace too.

My suggestion would be to remove the namespace object -- it's the safer way.

[f41gh7]

It make sense for me. May i ask to provide some example of usage or submit PR with needed changes?

[flokli]

This only seems to be an issue with the kustomize bits in the repo. When deploying via the helm chart, there's no monitoring-system namespace created or deployed to at all.