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

Fix prometheus alerts #2843

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Fix prometheus alerts #2843

wants to merge 1 commit into from

Conversation

emosbaugh
Copy link
Member

What type of PR is this?

type::feature

What this PR does / why we need it:

Fixes alerts

"KubeScheduler has disappeared from Prometheus target discovery."
"KubeControllerManager has disappeared from Prometheus target discovery."
"KubeProxy has disappeared from Prometheus target discovery."

Which issue(s) this PR fixes:

Fixes NONE

Special notes for your reviewer:

Does this PR introduce a user-facing change?

TODO

Does this PR require documentation?

NONE

@emosbaugh emosbaugh added the type::feature An enhancement to an existing add on or feature label Apr 16, 2022
@emosbaugh emosbaugh force-pushed the fix-prometheus-alerts branch from 6b53968 to 3ae68c9 Compare April 16, 2022 20:53
@emosbaugh
Copy link
Member Author

I need to test kube-bench to see if this violates cis benchmark

@github-actions
Copy link
Contributor

@emosbaugh emosbaugh force-pushed the fix-prometheus-alerts branch from 3ae68c9 to 091d848 Compare April 16, 2022 21:09
@github-actions
Copy link
Contributor

@emosbaugh emosbaugh force-pushed the fix-prometheus-alerts branch from 091d848 to 8d4c570 Compare April 18, 2022 17:17
@github-actions
Copy link
Contributor

@emosbaugh emosbaugh force-pushed the fix-prometheus-alerts branch from 8d4c570 to 0b562d0 Compare April 18, 2022 18:58
@github-actions
Copy link
Contributor

@emosbaugh emosbaugh force-pushed the fix-prometheus-alerts branch from 0b562d0 to 069f40d Compare April 18, 2022 22:40
@github-actions
Copy link
Contributor

@xavpaice xavpaice force-pushed the fix-prometheus-alerts branch from d3c6767 to 53e4f3c Compare October 4, 2022 02:04
@xavpaice
Copy link
Member

xavpaice commented Oct 4, 2022

rebased against current main branch

@xavpaice
Copy link
Member

xavpaice commented Oct 4, 2022

IIUC, this change is effective for k8s 1.21? Wonder if we can split out the content of addons/prometheus/0.55.0-34.10.0 from the change to templates & patches, and have a separate commit to apply that to the various addon versions?

@emosbaugh
Copy link
Member Author

IIUC, this change is effective for k8s 1.21? Wonder if we can split out the content of addons/prometheus/0.55.0-34.10.0 from the change to templates & patches, and have a separate commit to apply that to the various addon versions?

This was a work in progress. I made some progress on fixing a few false positive alerts but not all. I can't remember if this was only for <= 1.21 or all versions of k8s. Yes I would suggest splitting out template code. This PR is not ready and needs more work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type::feature An enhancement to an existing add on or feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants