We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
k3s-io/k3s#3619
The text was updated successfully, but these errors were encountered:
Alert manager keep firing absent for the next job; kube-scheduler kube-proxy kube-controller
Sorry, something went wrong.
How did you fix this and know it was fixed? Specifically the duplicated metrics?
Hi, yes I fixed it following https://picluster.ricsanfre.com/docs/prometheus/#k3s-components-monitoring I mostly only have one remaining alert firing
ATM, this repo isn't sync with what is my real environment because for the last 6 month I've been working on securing the whole env.
But if needed I can work on providing what I've done
No branches or pull requests
k3s-io/k3s#3619
The text was updated successfully, but these errors were encountered: