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
add monitoring to kind #2190
add monitoring to kind #2190
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
a86fd6e
to
44dfb51
Compare
ea4741b
to
7cf75c9
Compare
Install a prometheus deployment that collect metrics from all the kubernetes components. Modify kube-proxy to listen for metrics in all addresses, it listen by default only in localhost. Once the cluster is destroyed, it dumps the prometheus snapshot as a tarball, so it can be analyzed locally. https://suraj.io/post/how-to-backup-and-restore-prometheus/
@aojea: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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/test-infra repository. I understand the commands that are listed here. |
I think we should discuss having a mode where e2e.test in k/k is responsible for installing monitoring and snapshotting it 🤔 |
let's fork this to k/k then, I really find it useful in the openshift CI, they do this metrics snapshoting
yeah. let's discuss it there |
Install a prometheus deployment that collect metrics from all
the kubernetes components.
Modify kube-proxy to listen for metrics in all addresses, it listen
by default only in localhost.
Once the cluster is destroyed, it dumps the prometheus snapshot
as a tarball, so it can be analyzed locally.
https://suraj.io/post/how-to-backup-and-restore-prometheus/