Skip to content

chore(container): update image ghcr.io/prometheus-community/charts/kube-prometheus-stack to v90 - autoclosed - #2616

Closed
daddy-ro[bot] wants to merge 1 commit into
mainfrom
renovate/ghcr.io-prometheus-community-charts-kube-prometheus-stack-90.x
Closed

chore(container): update image ghcr.io/prometheus-community/charts/kube-prometheus-stack to v90 - autoclosed#2616
daddy-ro[bot] wants to merge 1 commit into
mainfrom
renovate/ghcr.io-prometheus-community-charts-kube-prometheus-stack-90.x

Conversation

@daddy-ro

@daddy-ro daddy-ro Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
ghcr.io/prometheus-community/charts/kube-prometheus-stack (source) major 89.2.490.0.0

Release Notes

prometheus-community/helm-charts (ghcr.io/prometheus-community/charts/kube-prometheus-stack)

v90.0.0

kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.

What's Changed

New Contributors

Full Changelog: prometheus-community/helm-charts@kube-prometheus-stack-89.2.4...kube-prometheus-stack-90.0.0


Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@daddy-ro daddy-ro Bot added the type/major label Sep 6, 2026
@daddy-ro
daddy-ro Bot enabled auto-merge (squash) September 6, 2026 23:03
@daddy-ro

daddy-ro Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor Author

Caution

  • HelmRelease observability/kps: helm template observability/kps: execution error at (kube-prometheus-stack/templates/exporters/kubelet/servicemonitor.yaml:48:8): The control-plane ServiceMonitors authenticate by default with the Secret created by prometheus.serviceAccount.createTokenSecret, which is only rendered when prometheus.enabled and prometheus.serviceAccount.create are also true. Enable them, or set the serviceMonitor.authorization of each enabled control-plane component to a Secret you manage yourself, or to null to scrape without authentication.

Warning

  • OCIRepository observability/kube-prometheus-stack: major version bump 89.2.4 → 90.0.0 of the OCI source; check the upstream release notes for breaking changes

Note

1 resource changed across 1 app

konflate 0.6.3 · rendered 88ada28 · full diff →

jfroy added a commit that referenced this pull request Sep 7, 2026
…token

kube-prometheus-stack 90.0.0 drops `bearerTokenFile` from the control-plane
ServiceMonitors (prometheus-operator rejects it under
`arbitraryFSAccessThroughSMs.deny`, and Alloy silently drops those targets) and
authenticates through `authorization` + a Secret instead. The chart creates that
Secret itself only alongside its own Prometheus, which is disabled here, so
`helm template` hard-fails on the bump in #2616.

vmagent scrapes these targets, so point every enabled control-plane component at
a long-lived token Secret for the `vmagent-kantai` ServiceAccount — the same
identity the old `bearerTokenFile` resolved to.

Lands ahead of the bump: 89.2.4 has no `serviceMonitor.authorization` value, so
the only thing this changes on the current chart is creating the Secret.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XoBaidgnaAAUkvQRZCtVmC
jfroy added a commit that referenced this pull request Sep 7, 2026
kube-prometheus-stack 90.0.0 replaces `bearerTokenFile` on the control-plane
ServiceMonitors with `authorization` pointing at a Secret. The chart creates that
Secret only alongside its own Prometheus, which is disabled here, so the bump on
its own fails to render.

vmagent scrapes these targets, so point every enabled control-plane component at
a long-lived token Secret for the `vmagent-kantai` ServiceAccount — the same
identity the old `bearerTokenFile` resolved to.

Supersedes #2616.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XoBaidgnaAAUkvQRZCtVmC
jfroy added a commit that referenced this pull request Sep 7, 2026
kube-prometheus-stack 90.0.0 replaces `bearerTokenFile` on the control-plane
ServiceMonitors with `authorization` pointing at a Secret. The chart creates that
Secret only alongside its own Prometheus, which is disabled here, so the bump on
its own fails to render.

vmagent scrapes these targets, so every control-plane component that still
renders — coreDns, kubeApiServer, kubelet, kubeControllerManager, kubeEtcd,
kubeScheduler — points its `serviceMonitor.authorization` at a token Secret for
the `vmagent-kantai` ServiceAccount. That is the same identity the old
`bearerTokenFile` resolved to, so scraping is unchanged. kubeProxy and kubeDns
are disabled and never reach the template.

The Secret is a `kubernetes.io/service-account-token` populated by the token
controller from its annotation. A ServiceMonitor can only carry a credential by
Secret reference, so vmagent's own projected token is not reachable from one;
the trade is that this token is long-lived and does not expire.

The Kustomization now depends on victoria-metrics, which is where the
VictoriaMetrics operator creates the `vmagent-kantai` ServiceAccount. Without
that ServiceAccount the token controller deletes the Secret rather than
populating it.

Supersedes #2616.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XoBaidgnaAAUkvQRZCtVmC
jfroy added a commit that referenced this pull request Sep 7, 2026
kube-prometheus-stack 90.0.0 replaces `bearerTokenFile` on the control-plane
ServiceMonitors with `authorization` pointing at a Secret. The chart creates that
Secret only alongside its own Prometheus, which is disabled here, so the bump on
its own fails to render.

vmagent scrapes these targets, so every control-plane component that still
renders — coreDns, kubeApiServer, kubelet, kubeControllerManager, kubeEtcd,
kubeScheduler — points its `serviceMonitor.authorization` at a token Secret for
the `vmagent-kantai` ServiceAccount. That is the same identity the old
`bearerTokenFile` resolved to, so scraping is unchanged. kubeProxy and kubeDns
are disabled and never reach the template.

The Secret is a `kubernetes.io/service-account-token` populated by the token
controller from its annotation. A ServiceMonitor can only carry a credential by
Secret reference, so vmagent's own projected token is not reachable from one;
the trade is that this token is long-lived and does not expire.

The Kustomization now depends on victoria-metrics, which is where the
VictoriaMetrics operator creates the `vmagent-kantai` ServiceAccount. Without
that ServiceAccount the token controller deletes the Secret rather than
populating it.

Supersedes #2616.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XoBaidgnaAAUkvQRZCtVmC
jfroy added a commit that referenced this pull request Sep 7, 2026
kube-prometheus-stack 90.0.0 replaces `bearerTokenFile` on the control-plane
ServiceMonitors with `authorization` pointing at a Secret. The chart creates that
Secret only alongside its own Prometheus, which is disabled here, so the bump on
its own fails to render.

vmagent scrapes these targets, so every control-plane component that still
renders — coreDns, kubeApiServer, kubelet, kubeControllerManager, kubeEtcd,
kubeScheduler — points its `serviceMonitor.authorization` at a token Secret for
the `vmagent-kantai` ServiceAccount. That is the same identity the old
`bearerTokenFile` resolved to, so scraping is unchanged. kubeProxy and kubeDns
are disabled and never reach the template.

The Secret is a `kubernetes.io/service-account-token` populated by the token
controller from its annotation. A ServiceMonitor can only carry a credential by
Secret reference, so vmagent's own projected token is not reachable from one;
the trade is that this token is long-lived and does not expire.

The Kustomization now depends on victoria-metrics, which is where the
VictoriaMetrics operator creates the `vmagent-kantai` ServiceAccount. Without
that ServiceAccount the token controller deletes the Secret rather than
populating it.

Supersedes #2616.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XoBaidgnaAAUkvQRZCtVmC
@daddy-ro daddy-ro Bot changed the title chore(container): update image ghcr.io/prometheus-community/charts/kube-prometheus-stack to v90 chore(container): update image ghcr.io/prometheus-community/charts/kube-prometheus-stack to v90 - autoclosed Sep 7, 2026
@daddy-ro daddy-ro Bot closed this Sep 7, 2026
auto-merge was automatically disabled September 7, 2026 23:50

Pull request was closed

@daddy-ro
daddy-ro Bot deleted the renovate/ghcr.io-prometheus-community-charts-kube-prometheus-stack-90.x branch September 7, 2026 23:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants