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
If prometheus-adapter contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
What happened?:
Can anyone please upgrade Prometheus adapter to fix following CVE's
CVE-2013-4235 | MEDIUM
CVE-2016-20013 | HIGH
CVE-2016-2781 | MEDIUM
CVE-2017-11164 | HIGH
CVE-2022-3219 | LOW
CVE-2022-41409 | HIGH
CVE-2023-26604 | HIGH
CVE-2023-29383 | LOW
CVE-2023-45918 | MEDIUM
CVE-2023-50495 | MEDIUM
CVE-2023-7008 | MEDIUM
CVE-2024-2236 | MEDIUM
CVE-2024-34155 | MEDIUM
CVE-2024-34156 | HIGH
CVE-2024-34158 | HIGH
What did you expect to happen?:
Fix the CVE
Please provide the prometheus-adapter config:
NA
Please provide the HPA resource used for autoscaling:
NA
Please provide the HPA status:
Please provide the prometheus-adapter logs with -v=6 around the time the issue happened:
NA
Anything else we need to know?:
Environment:
kubectl version
):The text was updated successfully, but these errors were encountered: