Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(container): update kube-prometheus-stack ( 65.5.1 → 65.8.1 ) - autoclosed #1483

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 4, 2024

This PR contains the following updates:

Package Update Change
kube-prometheus-stack (source) minor 65.5.1 -> 65.8.1

Release Notes

prometheus-community/helm-charts (kube-prometheus-stack)

v65.8.1

Compare Source

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-65.8.0...kube-prometheus-stack-65.8.1

v65.8.0

Compare Source

v65.7.0

Compare Source

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

Full Changelog: prometheus-community/helm-charts@prometheus-node-exporter-4.42.0...kube-prometheus-stack-65.7.0

v65.6.0

Compare Source

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

Full Changelog: prometheus-community/helm-charts@prometheus-25.29.0...kube-prometheus-stack-65.6.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title feat(container): update kube-prometheus-stack ( 65.5.1 → 65.6.0 ) feat(container): update kube-prometheus-stack ( 65.5.1 → 65.7.0 ) Nov 5, 2024
@renovate renovate bot force-pushed the renovate/kube-prometheus-stack-65.x branch from 841af9b to 9001b29 Compare November 5, 2024 12:25
@renovate renovate bot changed the title feat(container): update kube-prometheus-stack ( 65.5.1 → 65.7.0 ) feat(container): update kube-prometheus-stack ( 65.5.1 → 65.8.0 ) Nov 5, 2024
@renovate renovate bot force-pushed the renovate/kube-prometheus-stack-65.x branch from 9001b29 to 4f095f0 Compare November 5, 2024 22:25
@renovate renovate bot changed the title feat(container): update kube-prometheus-stack ( 65.5.1 → 65.8.0 ) feat(container): update kube-prometheus-stack ( 65.5.1 → 65.8.1 ) Nov 6, 2024
@renovate renovate bot force-pushed the renovate/kube-prometheus-stack-65.x branch 2 times, most recently from 0e6f5c4 to 0825e4a Compare November 7, 2024 13:23
@renovate renovate bot force-pushed the renovate/kube-prometheus-stack-65.x branch from 0825e4a to 851e40f Compare November 9, 2024 03:02
@renovate renovate bot changed the title feat(container): update kube-prometheus-stack ( 65.5.1 → 65.8.1 ) feat(container): update kube-prometheus-stack ( 65.5.1 → 65.8.1 ) - autoclosed Nov 10, 2024
@renovate renovate bot closed this Nov 10, 2024
@renovate renovate bot deleted the renovate/kube-prometheus-stack-65.x branch November 10, 2024 21:20
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