-
Notifications
You must be signed in to change notification settings - Fork 7
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
the controller doesn't update EP after the first run #4
Comments
The controller actually did the update but its like minutes after. And when scaling up/down. There is a gap when the service EP got revert back to cluster IP. |
i meet the same issue, and by my test it can cost up to ~10min to update secondary endpoints. |
hi, i'm not sure if this PR could solve the issue, but it works fine for me i guess the origin processNextWorkItem() discard some update events which not get ready because sync() returns errors for them @dolphyvn i built a image to fix this and hope useful to you:
|
@wardenlym I just tried using your docker image but the EP addresses are not showing up. POD:
POD status:
service:
service status:
Any idea why the EP IP is not showing? |
The controller unlikely to update EP after the first run. I have to restart it so the EP get update.
Anyone have same issue?
The text was updated successfully, but these errors were encountered: