[kube-prometheus-stack] set explicit HTTPRoute backendRef defaults#6719
Merged
jkroepke merged 3 commits intoprometheus-community:mainfrom Mar 15, 2026
Conversation
Signed-off-by: Firas Mosbehi <firas.mosbehi@insat.ucar.tn>
jkroepke
previously approved these changes
Mar 6, 2026
Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de>
Signed-off-by: Ilia Lazebnik <Ilia.lazebnik@gmail.com>
jkroepke
approved these changes
Mar 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR explicitly sets default backendRef fields (
group,kind,weight) in kube-prometheus-stack HTTPRoute templates, addressing #6441.Problem
Gateway API defaulting adds backendRef fields server-side. Because the chart omitted these fields, GitOps tools (for example Argo CD) can observe perpetual diff churn: desired manifests omit fields while live objects include defaulted values.
Root cause
Route templates only rendered backendRef
nameandportfor Prometheus, Alertmanager, and Thanos Ruler HTTPRoutes.Fix
Updated all three route templates to explicitly render:
group: ""kind: Serviceweight: 1alongside existing
nameandport.Files updated:
templates/prometheus/route.yamltemplates/alertmanager/route.yamltemplates/thanos-ruler/route.yaml82.9.0 -> 82.9.1Validation
helm lint charts/kube-prometheus-stackhelm template test charts/kube-prometheus-stack --set prometheus.route.main.enabled=truegroup,kind, andweight.Compatibility
No functional behavior change for routing semantics; this aligns rendered manifests with Kubernetes-defaulted live state.