Skip to content
Snippets Groups Projects
Select Git revision
  • 1d5dec22b9e4255c5133599b875476c07f63587d
  • main default protected
  • automated-updates-main
  • release-0.14
  • 14-env
  • fix-version-3
  • automated-updates-fix-action
  • release-0.15
  • release-0.13
  • automated-updates-release-0.13
  • release-0.10
  • release-0.11
  • release-0.12
  • fix-versions-action
  • versions-fix
  • release-0.9
  • release-0.8
  • release-0.7
  • release-0.6
  • release-0.5
  • release-0.4
  • v0.15.0
  • v0.14.0
  • v0.13.0
  • v0.12.0
  • v0.11.0
  • v0.10.0
  • v0.9.0
  • v0.8.0
  • v0.7.0
  • v0.6.0
  • v0.5.0
  • v0.4.0
  • v0.3.0
  • v0.2.0
  • v0.1.0
36 results

components-name-namespace-overrides.md

Blame
  • user avatar
    ArthurSens authored
    With the objective of improving our README, customization examples are being moved to a dedicated folder under `docs/`.
    
    Signed-off-by: default avatarArthurSens <arthursens2005@gmail.com>
    af00060d
    History
    components-name-namespace-overrides.md 2.41 KiB

    Components' name and namespace overrides

    It is possible to override the namespace where kube-prometheus is going to be deployed, like the example below:

    local kp = (import 'kube-prometheus/main.libsonnet') +
    {
      values+:: {
        common+: {
          namespace: 'monitoring',
        },
      },
    };

    If prefered, it can be changed individually by component. It is also possible to change the name of Prometheus and Alertmanager Custom Resources, like shown below:

    local kp = (import 'kube-prometheus/main.libsonnet') +
               {
                 values+:: {
                   common+: {
                     namespace: 'monitoring',
                   },
    
                   prometheus+: {
                     namespace: 'foo',
                     name: 'bar',
                   },
    
                   alertmanager+: {
                     namespace: 'bar',
                     name: 'foo',
                   },
                 },
               };
    
    { 'setup/0namespace-namespace': kp.kubePrometheus.namespace } +
    // Add the restricted psp to setup
    {
      ['setup/prometheus-operator-' + name]: kp.prometheusOperator[name]
      for name in std.filter((function(name) name != 'serviceMonitor' && name != 'prometheusRule'), std.objectFields(kp.prometheusOperator))
    } +
    // serviceMonitor and prometheusRule are separated so that they can be created after the CRDs are ready
    { 'prometheus-operator-serviceMonitor': kp.prometheusOperator.serviceMonitor } +
    { 'prometheus-operator-prometheusRule': kp.prometheusOperator.prometheusRule } +
    { 'kube-prometheus-prometheusRule': kp.kubePrometheus.prometheusRule } +
    { ['alertmanager-' + name]: kp.alertmanager[name] for name in std.objectFields(kp.alertmanager) } +
    { ['blackbox-exporter-' + name]: kp.blackboxExporter[name] for name in std.objectFields(kp.blackboxExporter) } +
    { ['grafana-' + name]: kp.grafana[name] for name in std.objectFields(kp.grafana) } +
    { ['kube-state-metrics-' + name]: kp.kubeStateMetrics[name] for name in std.objectFields(kp.kubeStateMetrics) } +
    { ['kubernetes-' + name]: kp.kubernetesControlPlane[name] for name in std.objectFields(kp.kubernetesControlPlane) }
    { ['node-exporter-' + name]: kp.nodeExporter[name] for name in std.objectFields(kp.nodeExporter) } +
    { ['prometheus-' + name]: kp.prometheus[name] for name in std.objectFields(kp.prometheus) } +
    { ['prometheus-adapter-' + name]: kp.prometheusAdapter[name] for name in std.objectFields(kp.prometheusAdapter) }