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
merge master into 4.3 #424
merge master into 4.3 #424
Conversation
I haven't been involved in this project for a long time, and I'm not in a position to review or approve any changes. Removing myself from OWNERS so the bot doesn't ask me to review stuff.
Remove myself from OWNERS
Currently we don't report that status. This fixes it. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1727024
It was accidentally reenabled in e62c9ac. This fixes it. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1734284
Bug 1734284: kube-apiserver ServiceMonitor is still in cluster-monitoring-operator
Co-Authored-By: Lili Cosic <cosiclili@gmail.com>
Bug 1727024: Add OperatorUpgradeable status to StatusReporter
…points There is no alert that reports when an etcd quorum member is degraded. Add an alert that reports if any etcd member is down or potentially unreachable. Since it is possible if the etcd metrics are collected under a Kubernetes service and the etcd instance is removed from the endpoint (due to implementation details of how etcd is run), extend the alert to also capture failure rate of requests to that cluster.
OWNERS: add LiliC
manifests: reduce logs verbosity for cluster-monitoring-operator
Bug 1734540: etcd should still alert when a member disappears from the endpoints
This is needed by kube-prometheus.
jsonnetfile.lock.json: Bump kube-prometheus
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LiliC, s-urbaniak 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 |
this is just a mechnical bump, such that
master-4.3
keeps up with the changes in the currentmaster
(4.2) branch./cc @lilic