How to deploy kube-prometheus Helm chart into a custom namespace (e.g., platform-observability)?

[Nikola-Milovic]

Hi kube-prometheus team,

We’re deploying kube-prometheus via Flux and would like all chart resources to live in a custom namespace platform- observability instead of the default monitoring.

Sample of our current Flux Kustomization (dev):

  apiVersion: kustomize.toolkit.fluxcd.io/v1
  kind: Kustomization
  metadata:
    name: kube-prometheus
    namespace: flux-system
  spec:
    sourceRef:
      kind: GitRepository
      name: kube-prometheus
      namespace: flux-system
    path: ./manifests
    targetNamespace: platform-observability   # <— desired namespace
    patches: [...]  # we delete bundled Grafana, tweak storage, etc.

Questions:

1. What’s the supported way to set the release namespace for the chart/manifests?
2. Is there a Helm value (or documented patch) to ensure CRDs/ClusterRoles stay cluster-scoped but namespaced resources
   (Deployments, Services, ServiceAccounts, secrets) land in platform-observability?
3. Any pitfalls with alertmanager/Prometheus selectors or RBAC when moving off the default monitoring namespace?
4. Is it okay to disable grafana and have it managed via a separate helm release?

Thanks!