-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
fix: extdns crashes when virtual service points to nonexistent … #3686
fix: extdns crashes when virtual service points to nonexistent … #3686
Conversation
Welcome @rumstead! |
/ok-to-test |
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.
It's not crashing, it's refusing to reconcile. A better commit message would be something like "ignore VirtualServices which reference a nonexistent Gateway"
Can you elaborate on why you think the container isn’t crashing? It’s getting to the |
Man, I even LGTMed that change to |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rumstead, szuecs 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 |
Signed-off-by: rumstead <[email protected]> updating test Update source/istio_virtualservice_test.go Co-authored-by: John Gardiner Myers <[email protected]> Update source/istio_virtualservice_test.go Co-authored-by: John Gardiner Myers <[email protected]>
/lgtm |
Thanks for the quick turnaround and review @johngmyers and @szuecs |
Is there any forecast for a release to be generated with this fix? |
We are waiting for this fix as well |
Yea, we are seeing this more and more as we roll out istio adoption. Would be great to have this released. |
Description
As of 0.13.5, a nonexistent gateway referenced by a virtual service causes external-dns to exit here, which means a developer could accidentally take down external-dns by deploying an invalid VirtualService.
Fixes #3628
Checklist