cmur2 / promgen-k8s

A modular Prometheus 2 configuration file generator to monitor multiple Kubernetes clusters with a single Prometheus instance.

promgen-k8s

A modular Prometheus 2 configuration file generator to monitor multiple Kubernetes clusters with a single Prometheus instance.

Scenario

You have one Kubernetes cluster per environment (dev, qa, staging, production, etc.) for whichever reasons including e.g. special permission model, limiting the blast radius of problems related to Kubernetes or to test Kubernetes upgrades in staging environment first. You have a separate Kubernetes cluster for operations that runs your monitoring and logging setup, CI pipeline, etc. You want to monitor all environments/clusters with a single Prometheus instance located in the operations cluster.

Writing, modifying and maintaining the prometheus.yml for one Kubernetes cluster by hand is tedious and error prone. Doing so for multiple clusters that should share most of the configuration except for specific rules can become a nightmare.

promgen-k8s aims to provide a toolkit allowing you to easily generate a prometheus.yml tailored for monitoring multiple Kubernetes clusters with invididual scraping jobs and relabeling rules per cluster.

Current State

promgen-k8s is currently in a very early state where it manages to generate the example prometheus-kubernetes.yml for multiple clusters using autodiscovery including custom relabeling rules per cluster. It assumes that it can reach all Kubernetes apiservers by predictable DNS names using the provided secret files for authentication.

For ingresses, pod, service and service endpoint monitoring in remote clusters promgen-k8s uses the Kubernetes apiservers as an HTTP proxy.

As ingresses and services are checked using the blackbox-exporter promgen-k8s also assumes a blackbox-exporter pod and service in monitoring namespace running in each cluster (including remote clusters).

promgen-k8s is successfully used with Kubernetes 1.8 clusters on AWS created by kops.

Example

The example uses a stub file for manual configuration and can be tested using pip install promgen-k8s and then python example-generator.py.

Related Work

• https://github.com/line/promgen

Doing a Release

You need to have the Poetry dependency manager installed and a PyPI account (a test account works as well) including an authentication token.

Testing the Release

One-time setup:

poetry config repositories.testpypi https://test.pypi.org/legacy/
poetry config pypi-token.testpypi TOKEN_FROM_TESTPYPI_ACCOUNT

Bump version in pyproject.toml, update the changelog with new release and date and commit.

Build and release:

poetry publish -r testpypi --build

Check installation:

pip install --index-url https://test.pypi.org/simple/ promgen_k8s

Official Release

One-time setup:

poetry config pypi-token.pypi TOKEN_FROM_PYPI_ACCOUNT

Bump version in pyproject.toml, update the changelog with new release and date and commit.

Build and release:

poetry publish --build

Check installation:

pip install promgen_k8s

License

promgen-k8s is licensed under the Apache License, Version 2.0. See LICENSE for more information.

promgen-k8s's Issues

Dependency Dashboard

View repository job log here.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• ci: update actions/setup-python action to v5

Detected dependencies

github-actions

.github/workflows/ci.yml

• actions/checkout v4
• actions/setup-python v4
• actions/checkout v4

pep621

pyproject.toml

• poetry >=1.0

poetry

pyproject.toml

• python ^3.7
• pyyaml *
• pylint *
• pytest *
• snapshottest *
• rope *
• toml *
• yapf *
• mypy *
• types-pyyaml *

---

• Check this box to trigger a request for Renovate to run again on this repository