-
Notifications
You must be signed in to change notification settings - Fork 157
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
Enable --enable-aggregator-routing by default #220
Enable --enable-aggregator-routing by default #220
Conversation
👍 |
Further context: even if networking were long-run 100% reliable, kube-proxy still has non-zero convergence time. In times of apiserver disruption, this naturally can take longer, which would exacerbate any problems. This change takes one more component out of the critical path. |
/retest |
2 similar comments
/retest |
/retest |
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
@deads2k fyi, we've struggled with this on Friday with Stefan when we encountered API server flapping again
edefee6
to
b21db69
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mfojtik, soltysh, sttts 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 |
/retest |
1 similar comment
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
Use endpoints IPs directly instead of service IPs, taking some of the networking logic out of the (stability) equation.