Skip to content
Snippets Groups Projects
Select Git revision
  • b332c58421cf2c4cbe091202f6dc3c55e1b6a7fc
  • main default protected
  • dependabot/go_modules/k8s.io/client-go-0.33.4
  • dependabot/go_modules/k8s.io/apimachinery-0.33.4
  • 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
  • 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

platform-specific.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
    platform-specific.md 634 B

    Running kube-prometheus on specific platforms

    A common example is that not all Kubernetes clusters are created exactly the same way, meaning the configuration to monitor them may be slightly different. For the following clusters there are mixins available to easily configure them:

    • aws
    • bootkube
    • eks
    • gke
    • kops
    • kops_coredns
    • kubeadm
    • kubespray

    These mixins are selectable via the platform field of kubePrometheus:

    (import 'kube-prometheus/main.libsonnet') +
    {
      values+:: {
        common+: {
          platform: 'example-platform',
        },
      },
    }