You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i'm working in a cluster where resources are rare so i'm looking to decrease the footprint of my deployments. To enable this i'd like to reduce the number of Replicasets that's kept as there's a resource quota for that as well.
Describe the solution you'd like.
I'd like to be able to set the revisionHistoryLimit for the prometheus-blackbox exporter - as I use most exporters more like "up and running or ready to troubleshoot" and don't use helm rollbacks. So i'd like to reduce the replicaset overhead by setting the revisionHistoryLimit lower
Describe alternatives you've considered.
currently i'm working with helmfiles strategicMergePatches workaround to still set the revisionHistoryLimit lower than the default of 10..
Additional context.
No response
The text was updated successfully, but these errors were encountered:
CarstenSon
changed the title
[all deployment resources] make revisionHistoryLimit customizable
[prometheus-blackbox-exporter] make revisionHistoryLimit customizable
Jan 29, 2025
Is your feature request related to a problem ?
i'm working in a cluster where resources are rare so i'm looking to decrease the footprint of my deployments. To enable this i'd like to reduce the number of Replicasets that's kept as there's a resource quota for that as well.
Describe the solution you'd like.
I'd like to be able to set the revisionHistoryLimit for the prometheus-blackbox exporter - as I use most exporters more like "up and running or ready to troubleshoot" and don't use helm rollbacks. So i'd like to reduce the replicaset overhead by setting the revisionHistoryLimit lower
Describe alternatives you've considered.
currently i'm working with helmfiles strategicMergePatches workaround to still set the revisionHistoryLimit lower than the default of 10..
Additional context.
No response
The text was updated successfully, but these errors were encountered: