Crazy at it sounds, some Kubernetes installations don't have access to Internet
and source all their images from an internal registry.
sync-to-internal-registry.jsonnet is a jsonnet snippet that helps with the task
of pushing upstream images used by the prometheus operator to an internal
registry by printing the right docker pull/tag/push commands.
$ jsonnet -J vendor -S --tla-str repository=internal-registry.com/organization sync-to-internal-registry.jsonnet
docker pull quay.io/coreos/addon-resizer:1.0
docker tag quay.io/coreos/addon-resizer:1.0 internal-registry.com/organization/addon-resizer:1.0
docker push internal-registry.com/organization/addon-resizer:1.0
docker pull quay.io/prometheus/alertmanager:v0.15.2
docker tag quay.io/prometheus/alertmanager:v0.15.2 internal-registry.com/organization/alertmanager:v0.15.2
docker push internal-registry.com/organization/alertmanager:v0.15.2
...
contrib/kube-prometheus: Generate new manifests with antiAffinity
contrib/kube-prometheus: jb update
Documentation: Generate after updating kube-prometheus manifests
contrib/kube-prometheus: Move antiaffinity into own jsonnet file
foobar
This is distributed as a library that the user is meant to import.
example:
```
kp = (import 'kube-prometheus/kube-prometheus.libsonnet') +
(import 'kube-prometheus/kube-prometheus-thanos.libsonnet') +
{
_config+:: {...}
};
```
Only trigger disk running full alerts when the disk capacity is over 85%
and use recording rule of the kubernetes-mixin to only consider real
physical filesystems.
Currently, we are mounting `/root` from the host as `/host/root`.
Instead simply `/` from the host should be mounted.
This fixes it
Signed-off-by: Sergiusz Urbaniak <sergiusz.urbaniak@gmail.com>
This commit bumps the version of the Prometheus Operator jsonnet
dependency in kube-prometheus. With this change, kube-prometheus now
supports Prometheus Operator v0.23.0.
As requested, this updates the resource specification to live directly in config.kubeStateMetrics
It also clarifies the config variables. These names are what google uses in some of their tooling.
(And a slight tweak to the way collectors are specified)
As I work with kube-state-metrics in a large cluster, I found I needed to make some adjustments.
- Expose the collectors, allowing one to configure exclusions.
- Expose the addon_resizer parameters, facilitating reproduce adjustments
- Allow adjusting scrapeTimeout and scrapeInterval
