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

Upgrading Clusterloader2 Prometheus-operator Pkgs #3001

Open
Miseratio opened this issue Nov 18, 2024 · 1 comment
Open

Upgrading Clusterloader2 Prometheus-operator Pkgs #3001

Miseratio opened this issue Nov 18, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@Miseratio
Copy link

What would you like to be added:
Upgrade the Prometheus-related packages and manifests used by ClusterLoader2 to newer versions.

Why is this needed:
I am a developer currently working on benchmarking a custom Kubernetes cluster and have noticed that the Prometheus packages and images relied upon by ClusterLoader2 are outdated and lack modularization. To be specific, the Prometheus manifests were last updated to version 0.46.0 three years ago.

The Prometheus Operator repository now provides kube-prometheus, a dedicated package tailored for Kubernetes environments. However, the newer Prometheus images are incompatible with the existing outdated manifests in ClusterLoader2, making updates challenging. A specific example of upgrade benefit is the node-exporter DaemonSet listed in the TODO comments of the prometheus.go, which is already implemented in the kube-prometheus package but remains incomplete in ClusterLoader2.

Additionally, updating to newer image versions would help address CVEs in older versions, ensuring a more secure and reliable benchmarking environment. This upgrade would modernize ClusterLoader2, resolve compatibility issues with new images, and enhance the maintainability of benchmarking workflows.

@Miseratio Miseratio added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 18, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants