-
Notifications
You must be signed in to change notification settings - Fork 36
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
Explicit fallthrough is needed while request does not match configured zones #956
Comments
CC @vthapar |
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
@vthapar can you take a look at this? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
While demonstrating #954, I found that explicit
fallthrough
is needed while request does not match configured zones, and this is different with behavior ofkubernetes
andmulticluster
. Iffallthrough
not configured,NOTZONE
will be returned.I found this change is introduced by 744b666. Could you please kindly clarify if there's any specific consideration, or we can just align the code with
kubernetes
:The text was updated successfully, but these errors were encountered: