-
Notifications
You must be signed in to change notification settings - Fork 112
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
UPSTREAM: <carry>: add audit annotations to track etcd state #2170
base: master
Are you sure you want to change the base?
Conversation
@deads2k: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
Comment |
very strange /retest |
We can reconsider this if we have field size issues, but I doubt we will. If we do, we can find a way to configure this only during pre-release we gain a lot of useful CI data.
cccaf3c
to
bc8ac76
Compare
@deads2k: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
Comment |
/lgtm Discussed and accepted the increase in the serialized size of audit log entries in exchange for having the latency annotations all the time. /hold for proof |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: benluddy, deads2k 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 No "no leader" annotations in the audit, but clients definitely say they appeared. Who's lying! I'll check in the morning |
@deads2k: The following tests failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
We can use these annotations in a monitortest to start counting how many seconds we appear to lose etcd leadership for and what percentage of etcd requests fail during that time.