Closed tjungblu closed 8 months ago
@tjungblu: This pull request references Jira Issue OCPBUGS-29717, which is invalid:
Comment /jira refresh
to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
/jira refresh
@tjungblu: This pull request references Jira Issue OCPBUGS-29717, which is valid. The bug has been moved to the POST state.
Requesting review from QA contact: /cc @geliu2016
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Elbehery, geliu2016, tjungblu
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/retest
@geliu2016 thanks, but I believe your label didn't come through :rofl:
@tjungblu: The following tests failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
ci/prow/e2e-aws-etcd-recovery | 81efbfeca962ea68c221b919a9b2439cd96f94ef | link | false | /test e2e-aws-etcd-recovery |
ci/prow/e2e-gcp-qe-no-capabilities | 81efbfeca962ea68c221b919a9b2439cd96f94ef | link | false | /test e2e-gcp-qe-no-capabilities |
Full PR test history. Your PR dashboard.
/label backport-risk-assessed
/cherry-pick release-4.14
@geliu2016 could you label again please? I think it didn't come through
@tjungblu: once the present PR merges, I will cherry-pick it on top of release-4.14 in a new PR and assign it to you.
/label cherry-pick-approved
@tjungblu: Jira Issue OCPBUGS-29717: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-29717 has been moved to the MODIFIED state.
@tjungblu: new pull request created: #1211
[ART PR BUILD NOTIFIER]
This PR has been included in build cluster-etcd-operator-container-v4.15.0-202402280108.p0.gb1dc0a7.assembly.stream.el9 for distgit cluster-etcd-operator. All builds following this will include this PR.
From profiling on cert rotation we know that the node informer is called every couple of seconds on node heartbeats. This PR will ensure that all our node listers only ever listen/inform on the master node updates to reduce the frequency of unnecessary sync calls.