easylinux/kube-prometheus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
2,857 Commits 19 Branches 14 Tags
158cb5422ebe95a7cad82efe0999bcff1d764443
Commit Graph
6 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
Joao MarcalandGitHub 7363e20b65 Adds startupProbe to prometheus-adapter (#2029) 
Issue: https://issues.redhat.com/browse/OCPBUGS-7694

Problem: in clusters with a large nb of CRDs deployed prom-adapter takes too long to discover all of them which makes it fail the livenessProbe

Solution: introduce a startupProbe that gives 3 minutes for prom-adapter to initialize

Signed-off-by: JoaoBraveCoding <jmarcal@redhat.com>
 2023-03-14 15:39:30 +00:00
Joao MarcalandGitHub 0a073679c6 Updates Prometheus Adapater version to 0.10.0 (#1865) 
Updates Prometheus Adapater image to official image documented in
kubernetes-sigs/prometheus-adapter/README.md
 2022-09-06 15:30:55 +01:00
Joao Marcal cf36ffb335 Adds YAML for jsonnet modified for prometheus-adapter 2022-03-30 15:35:36 +01:00
Joao Marcal 1d46f7ece9 Adds port name to prometheus-adapter jsonnet 2022-03-30 15:34:40 +01:00
Joao Marcal 652c6d538e Adds YAML for jsonnet modified in the previous commit 2022-03-30 07:23:05 +01:00
Joao Marcal f6190e200a Adds readinessProbe and livenessProbe to prometheus-adapter jsonnet 
Problem: Currently the prometheus-adapter pods are restarted at the same
time even though the deployment is configured with strategy RollingUpdate.
This happens because the kubelet does not know when the prometheus-adapter
pods are ready to start receiving requests.

Solution: Add both readinessProbe and livenessProbe to the
prometheus-adapter, this way the kubelet will know when either the pod
stoped working and should be restarted or simply when it ready to start
receiving requests.

Issue: https://bugzilla.redhat.com/show_bug.cgi?id=2048333
 2022-03-30 07:22:55 +01:00