-
Notifications
You must be signed in to change notification settings - Fork 70
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
Secure metrics server #119
Secure metrics server #119
Conversation
d8afe6a
to
cd3c7a0
Compare
0e975fe
to
ffadb0e
Compare
@spangenberg can we please make sure there's an e2e test that validates metrics are reported before merging this |
/hold |
e85fedc
to
008e436
Compare
008e436
to
16ae115
Compare
16ae115
to
07d5c86
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
@enxebre just validated positively that the |
/hold cancel |
/retest Please review the full test history for this PR and help us cut down flakes. |
21 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
This is breaking all CI due to alert being trieggered openshift#119
The cluster-version operator is responsible for complaining if the autoscaler operator's deployment is sad, so no need for the operator to handle this directly (we end up doubling up if there's an issue). This drops the alert which was originally added in e1d8025 (Add autoscaler down prometheus rule, 2019-11-05, openshift#119).
The cluster-version operator is responsible for complaining if the autoscaler operator's deployment is sad, so no need for the operator to handle this directly (we end up doubling up if there's an issue). This drops the alert which was originally added in e1d8025 (Add autoscaler down prometheus rule, 2019-11-05, openshift#119).
No description provided.