Open JokerDevops opened 7 months ago
You need to use the -config-reloader-cpu-*
and -config-reloader-memory-*
args of the Prometheus operator.
This issue has been automatically marked as stale because it has not had any activity in the last 60 days. Thank you for your contributions.
You need to use the
-config-reloader-cpu-*
and-config-reloader-memory-*
args of the Prometheus operator.
Does this only work after a certain version? I am running v0.67.1
and have the args set on my prometheus-operator
deployment but our alertmanager
config reloader container is not honoring the values. I skimmed the changelog for the operator and no mention of a bugfix or anything related to these args afaict.
- args:
- --kubelet-service=kube-system/kubelet
- --prometheus-config-reloader=quay.io/prometheus-operator/prometheus-config-reloader:v0.67.1
- --config-reloader-cpu-limit=20m
- --config-reloader-memory-limit=50Mi
- --config-reloader-cpu-request=20m
- --config-reloader-memory-request=50Mi
image: quay.io/prometheus-operator/prometheus-operator:v0.67.1
Nevermind, found the bugfix! https://github.com/prometheus-operator/prometheus-operator/pull/5971
This issue has been automatically marked as stale because it has not had any activity in the last 60 days. Thank you for your contributions.
How can I adjust the resources of the config-reloader container in alertmanager?
It is always 10m and 50Mi