[stable/prometheus-operator] Ability to configure namespace

[arruzk]

I would like to create a chart which will depend on prometheus-operator and I want to install prometheus in a separate namespace.

dependencies:
  - name: prometheus-operator
    version: "7.2.0"
    repository: "@stable"

Currently it's not possible to specify different namespace for prometheus (namespace: {{ $.Release.Namespace }}).

Is it a better way than fork the chart and change it to something like namespace: {{ .Values.global.prometheusNamespace }}?

[vsliouniaev]

Look at the helm --namespace parameter

[arruzk]

@vsliouniaev namespace from this parameter is used for deploying the main chart. I would like to install prometheus operator to the separate one.

[vsliouniaev]

You want to put portions of the chart into one namespace and other parts into another namespace? I don't really understand the reasoning for doing this

[arruzk]

@vsliouniaev the idea is not to mix "service" pods\services\secrets (eg from prometheus operator) with my own applications.
I can install prometheus and my own applications as a different helm releases, but one of my application depends on prometheus. For this reason I included it as a dependency, but it's not very convenient to have this mix.

Here is an example of similar problem and solution #15202

[vsliouniaev]

Thanks for the explanation! Feel free to submit a PR into this chart to get this functionality.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale]

This issue is being automatically closed due to inactivity.