close over the ingress variable or the last assignment will be used #433
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When you have more than one ingress per namespace and they are "mixed", the scoping on the ing variable will end up pointing to the last one assigned inside the go function.
This will cause the ingress to keep trying to update the ip and fight the GCE load balancer.
Without fix:
with the fix
You can see it starting to fight the GCE one fairly quickly on the unpatched, and the delightful lack of ip updating in the patched one.